[#97063] [Ruby master Bug#16608] ConditionVariable#wait should return false when timeout exceeded — shugo@...

Issue #16608 has been reported by shugo (Shugo Maeda).

10 messages 2020/02/05

[#97084] [Ruby master Feature#16614] New method cache mechanism for Guild — ko1@...

Issue #16614 has been reported by ko1 (Koichi Sasada).

18 messages 2020/02/07

[#97248] [Ruby master Bug#16651] Extensions Do Not Compile on Mingw64 — cfis@...

Issue #16651 has been reported by cfis (Charlie Savage).

17 messages 2020/02/24

[#97289] [Ruby master Bug#16658] `method__cache__clear` DTrace hook was dropped without replacement — v.ondruch@...

Issue #16658 has been reported by vo.x (Vit Ondruch).

9 messages 2020/02/27

[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...

Issue #16663 has been reported by headius (Charles Nutter).

29 messages 2020/02/28

[#97310] [Ruby master Feature#16665] Add an Array#except_index method — alexandr1golubenko@...

Issue #16665 has been reported by alex_golubenko (Alex Golubenko).

12 messages 2020/02/29

[ruby-core:97039] [Ruby master Feature#16602] Add support for `frozen_string_literals` to eval.

From: eregontp@...
Date: 2020-02-01 14:42:20 UTC
List: ruby-core #97039
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: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next