[#109115] [Ruby master Misc#18891] Expand tabs in C code — "k0kubun (Takashi Kokubun)" <noreply@...>

Issue #18891 has been reported by k0kubun (Takashi Kokubun).

13 messages 2022/07/02

[#109118] [Ruby master Bug#18893] Don't redefine memcpy(3) — "alx (Alejandro Colomar)" <noreply@...>

Issue #18893 has been reported by alx (Alejandro Colomar).

11 messages 2022/07/02

[#109152] [Ruby master Bug#18899] Inconsistent argument handling in IO#set_encoding — "javanthropus (Jeremy Bopp)" <noreply@...>

Issue #18899 has been reported by javanthropus (Jeremy Bopp).

10 messages 2022/07/06

[#109193] [Ruby master Bug#18909] ARGF.readlines reads more than current file — "JohanJosefsson (Johan Josefsson)" <noreply@...>

Issue #18909 has been reported by JohanJosefsson (Johan Josefsson).

17 messages 2022/07/13

[#109196] [Ruby master Bug#18911] Process._fork hook point is not called when Process.daemon is used — "ivoanjo (Ivo Anjo)" <noreply@...>

Issue #18911 has been reported by ivoanjo (Ivo Anjo).

9 messages 2022/07/13

[#109201] [Ruby master Bug#18912] Build failure with macOS 13 (Ventura) Beta — "hsbt (Hiroshi SHIBATA)" <noreply@...>

Issue #18912 has been reported by hsbt (Hiroshi SHIBATA).

20 messages 2022/07/14

[#109206] [Ruby master Bug#18914] Segmentation fault during Ruby test suite execution — "jprokop (Jarek Prokop)" <noreply@...>

Issue #18914 has been reported by jprokop (Jarek Prokop).

8 messages 2022/07/14

[#109207] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedYet — Quintasan <noreply@...>

Issue #18915 has been reported by Quintasan (Michał Zając).

18 messages 2022/07/14

[#109260] [Ruby master Feature#18930] Officially deprecate class variables — "Eregon (Benoit Daloze)" <noreply@...>

Issue #18930 has been reported by Eregon (Benoit Daloze).

21 messages 2022/07/20

[#109314] [Ruby master Bug#18938] Backport cf7d07570f50ef9c16007019afcff11ba6500d70 — "byroot (Jean Boussier)" <noreply@...>

Issue #18938 has been reported by byroot (Jean Boussier).

8 messages 2022/07/25

[#109371] [Ruby master Feature#18949] Deprecate and remove replicate and dummy encodings — "Eregon (Benoit Daloze)" <noreply@...>

Issue #18949 has been reported by Eregon (Benoit Daloze).

35 messages 2022/07/29

[ruby-core:109188] [Ruby master Bug#18905] :"@=".inspect is non-evaluatable

From: "ufuk (Ufuk Kayserilioglu)" <noreply@...>
Date: 2022-07-11 20:29:07 UTC
List: ruby-core #109188
Issue #18905 has been updated by ufuk (Ufuk Kayserilioglu).


I was bitten by the same thing last week and was actually going to open an issue myself. Thanks for raising this @qnighy.

The thing that caught me out was that the following discrepancy:
```ruby
"4_to_5".to_sym.inspect
#=> :"4_to_5"
"4_to_5=".to_sym.inspect
#=> :4_to_5=
```
I realize that Ruby spends a considerable amount of effort to not print symbols in a format where they could not be roundtripped, and the discprancy between `:"4_to_5"` and `:"4_to_5="` was surprising.

I bisected the change to the released versions of Ruby and found that the behaviour changed somewhere between `ruby-2.2.0-preview1` and `ruby-2.2.0-preview2`:

```
$ docker run --rm -e "ALL_RUBY_SINCE=ruby-2.0" rubylang/all-ruby ./all-ruby -e "puts '4_to_5='.to_sym.inspect"
ruby-2.0.0-p0       :"4_to_5="
...
ruby-2.2.0-preview1 :"4_to_5="
ruby-2.2.0-preview2 :4_to_5=
...
ruby-3.2.0-preview1 :4_to_5=
```

Looking at the commit log, I can see that there is a commit that adds special casing for a trailing `=` but I don't understand the reason behind why the change was made: https://github.com/ruby/ruby/commit/986a893d7a420b8472c06b2e36b71b8bf00e9e21 

@nobu I understand that Ruby does not guarantee that `inspect` methods are for `eval` but Ruby seems to consistently quote invalid `Symbol`s in `inspect`, except for when they end with `=`. I think this is not consistent and Ruby might as well not quote `Symbol`s in `inspect` at all, in this case. I think something has to change to keep consistency.

----------------------------------------
Bug #18905: :"@=".inspect is non-evaluatable
https://bugs.ruby-lang.org/issues/18905#change-98329

* Author: qnighy (Masaki Hara)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
There is an edge case where `Symbol#inspect` returns a non-evaluatable expression:

```ruby
:"@=".inspect # => :@=
:"[][]=".inspect # => :[][]=
:"$$$$=" # => :$$$$=
```

More specifically, the quotations are stripped if the following conditions are met (but the converse does not hold):

- It starts with `@`, `@@`, `$` or `[`,
- the prefix is not followed by an identifier, and
- it ends with `=`.

But the rule should only apply to `:$=` and `:[]=`, because (in my understanding) we should generally have `eval(sym.inspect) == sym` for the programmers' convenience.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next