From: eregontp@... Date: 2020-02-01T14:42:20+00:00 Subject: [ruby-core:97039] [Ruby master Feature#16602] Add support for `frozen_string_literals` to eval. Issue #16602 has been updated by Eregon (Benoit Daloze). ioquatix (Samuel Williams) wrote in #note-2: > Requires modification of the string which is sometimes messy. How is it messy? Isn't it as simple as @byroot showed? > `coding` too. Just using the encoding of the String seems much better for `eval`. > Requires modification of line numbers if you want to do it in a way which is not visible to the user. You can pass a line number to `eval` to make it look like there was no extra line. I think what @byroot says is sufficient. The global command-line flag is a very different thing that probably doesn't work for many gems. The way it's implemented currently is entirely consistent, the parser reads magic comments like `# frozen_string_literal: true` no matter where it's parsed from. Also, I think adding `# frozen_string_literal` to code not adding it itself is a potentially breaking change, so I think it doesn't need to be super convenient. Basically, it's back to the discussion of enabling `frozen_string_literal` by default. ---------------------------------------- Feature #16602: Add support for `frozen_string_literals` to eval. https://bugs.ruby-lang.org/issues/16602#change-84132 * 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: