messanjah messanjah - 4 months ago 5x
Ruby Question

What does the comment "frozen_string_literal: true" do?

This is the

binstub in my project directory.

#!/usr/bin/env ruby
load File.expand_path("../spring", __FILE__)
rescue LoadError
# frozen_string_literal: true
# This file was generated by Bundler.
# The application 'rspec' is installed as part of a gem, and
# this file is here to facilitate running it.

require "pathname"
ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",

require "rubygems"
require "bundler/setup"

load Gem.bin_path("rspec-core", "rspec")

What is this intended to do?

# frozen_string_literal: true


# frozen_string_literal: true is a magic comment, supported for the first time in Ruby 2.3, that tells Ruby that all string literals in the file are implicitly frozen, as if #freeze had been called on each of them. That is, if a string literal is defined in a file with this comment, and you call a method on that string which modifies it, such as <<, you'll get RuntimeError: can't modify frozen String.

The comment must be on the first line of the file.

In Ruby 2.3, you can use this magic comment to prepare for frozen string literals being the default in Ruby 3.

In Ruby 2.3 run with the --enable=frozen-string-literal flag, and in Ruby 3, string literals are frozen in all files. You can override the global setting with # frozen_string_literal: false.

If you want a string literal to be mutable regardless of the global or per-file setting, you can prefix it with the unary + operator (being careful with operator precedence) or call .dup on it:

# frozen_string_literal: true
=> true
=> false
=> false

You can also freeze a mutable (unfrozen) string with unary -.