[ruby-core:121141] [Ruby master Bug#21153] ::Foo ||= p 1 should parse
From:
"qnighy (Masaki Hara) via ruby-core" <ruby-core@...>
Date:
2025-02-23 01:28:10 UTC
List:
ruby-core #121141
Issue #21153 has been reported by qnighy (Masaki Hara).
----------------------------------------
Bug #21153: ::Foo ||= p 1 should parse
https://bugs.ruby-lang.org/issues/21153
* Author: qnighy (Masaki Hara)
* Status: Open
* ruby -v: ruby 3.5.0dev (2025-02-22T15:11:40Z master fd882fb681) +PRISM [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
There is an inconsistency between how `Foo` and `::Foo` are handled:
```console
% ./miniruby --parser=parse.y -e "Foo ||= p 1"
1
% ./miniruby --parser=parse.y -e "::Foo ||= p 1"
-e:1: syntax error, unexpected integer literal, expecting 'do' or '{' or '('
::Foo ||= p 1
./miniruby: compile error (SyntaxError)
```
Note that `Object::Foo` also parses.
Prism successfully parses both, which is what I expect.
```console
% ./miniruby --parser=prism -e "Foo ||= p 1"
1
% ./miniruby --parser=prism -e "::Foo ||= p 1"
1
```
To fix this, you should probably handle all tOP_ASGNs in the op_asgn rule.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/