[ruby-core:123440] [Ruby Bug#21187] Strings concatenated with `\` getting frozen with literal hashes (PRISM only)
From:
"k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>
Date:
2025-10-08 23:39:05 UTC
List:
ruby-core #123440
Issue #21187 has been updated by k0kubun (Takashi Kokubun).
Thanks for the instructions.
Could we just cut a release of Prism now? I think we could do more releases=
of Prism, which would make these backport tasks simpler.
I've heard that @kddnewton is okay with automating the gem release with tru=
sted publishing. Once we automate that along with crate/npm releases, I can=
cut a release myself whenever I need to backport the latest Prism.
----------------------------------------
Bug #21187: Strings concatenated with `\` getting frozen with literal hashe=
s (PRISM only)
https://bugs.ruby-lang.org/issues/21187#change-114811
* Author: LocoDelAssembly (Hern=E1n Pereira)
* Status: Closed
* Assignee: prism
* ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: REQUIRED
----------------------------------------
When the first elements of a literal hash are strings that are concatenated=
with `\`, those elements are flagged with `PM_NODE_FLAG_STATIC_LITERAL` an=
d a special optimization that I believe was introduced in https://github.co=
m/ruby/ruby/commit/8080de04be8e99e71309745822a9d436cc4ae37c causes the stri=
ngs to be frozen.
Reproduction
=3D=3D=3D
test.rb
```
a =3D {
a: 'one' \
'two',
b: 'three' \
'four',
c: 'five',
d: 'six' \
'seven'
}
b =3D {
a: 'one',
b: 'two' \
'three'
}
puts "a =3D #{a.map { |k,v| {k =3D> v.frozen?} }}"
puts "b =3D #{b.map { |k,v| {k =3D> v.frozen?} }}"
```
With prism:
```
$ ruby test.rb =20
a =3D [{a: true}, {b: true}, {c: false}, {d: false}]
b =3D [{a: false}, {b: false}]
```
With parse.y:
```
$ ruby --parser=3Dparse.y test.rb
a =3D [{a: false}, {b: false}, {c: false}, {d: false}]
b =3D [{a: false}, {b: false}]
```
(Notice `b` hash is unaffected in both parsers)
Not sure if this is just part of undefined behavior or this is indeed a bug=
. Assigning a string concatenated with `\` to a variable doesn't make it fr=
ozen, to the best of my knowledge this seems to be hash-specific.
--=20
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.rub=
y-lang.org/