From: sawadatsuyoshi@... Date: 2020-02-01T12:34:10+00:00 Subject: [ruby-core:97038] [Ruby master Feature#16602] Add support for `frozen_string_literals` to eval. Issue #16602 has been updated by sawa (Tsuyoshi Sawada). ioquatix (Samuel Williams) wrote in #note-2: > Yes, it does, but it: > - Requires modification of the string which is sometimes messy. It requires modification because it is indeed modification: You are adding specification to a piece of code that did not have such specification. > I think any option that can be provided on the comment line at the start should also be an option to `eval`, and `*_eval`. e.g. `coding` too. Once you start asking for such feature, it would be a matter of time that someone would ask for features like: ```ruby require "foo", frozen_string_literal: true load "bar.rb", frozen_string_literal: true ``` ---------------------------------------- Feature #16602: Add support for `frozen_string_literals` to eval. https://bugs.ruby-lang.org/issues/16602#change-84131 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- Would it make sense for `eval(..., frozen_string_literal: true)` to exist? -- https://bugs.ruby-lang.org/ Unsubscribe: