[#123172] [Ruby Bug#21560] RUBY_MN_THREADS=1 causes large performance regression in Puma 7 — "schneems (Richard Schneeman) via ruby-core" <ruby-core@...>

Issue #21560 has been reported by schneems (Richard Schneeman).

13 messages 2025/09/03

[#123197] [Ruby Misc#21566] Transfer Shopify/yjit-bench and speed.yjit.org to ruby/ruby-bench and *.ruby-lang.org — "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>

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

7 messages 2025/09/08

[#123207] [Ruby Bug#21568] Requiring core libraries when already requiring mutliple user defined libraries with the same name can error — "alexalexgriffith (Alex Griffith) via ruby-core" <ruby-core@...>

Issue #21568 has been reported by alexalexgriffith (Alex Griffith).

9 messages 2025/09/10

[#123209] [Ruby Bug#21569] [armv7, musl] SIGBUS in ibf_load_object_float due to unaligned VFP double load when reading IBF — "amacxz (Aleksey Maximov) via ruby-core" <ruby-core@...>

SXNzdWUgIzIxNTY5IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGFtYWN4eiAoQWxla3NleSBNYXhpbW92

8 messages 2025/09/10

[#123257] [Ruby Misc#21606] DevMeeting-2025-10-23 — "mame (Yusuke Endoh) via ruby-core" <ruby-core@...>

Issue #21606 has been reported by mame (Yusuke Endoh).

9 messages 2025/09/16

[#123261] [Ruby Bug#21607] require 'concurrent-ruby' causes segfault with Ruby 3.4.6 on linux/i686 — "satadru (Satadru Pramanik) via ruby-core" <ruby-core@...>

Issue #21607 has been reported by satadru (Satadru Pramanik).

17 messages 2025/09/16

[#123279] [Ruby Misc#21609] Propose Stan Lo (@st0012) as a core committer — "tekknolagi (Maxwell Bernstein) via ruby-core" <ruby-core@...>

SXNzdWUgIzIxNjA5IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IHRla2tub2xhZ2kgKE1heHdlbGwgQmVy

12 messages 2025/09/17

[#123288] [Ruby Bug#21610] Use ec->interrupt_mask to prevent interrupts. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

SXNzdWUgIzIxNjEwIGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGlvcXVhdGl4IChTYW11ZWwgV2lsbGlh

7 messages 2025/09/18

[#123319] [Ruby Feature#21615] Introduce `Array#values` — "matheusrich (Matheus Richard) via ruby-core" <ruby-core@...>

Issue #21615 has been reported by matheusrich (Matheus Richard).

9 messages 2025/09/23

[#123350] [Ruby Bug#21618] Allow to use the build-in prism version to parse code — "Earlopain (Earlopain _) via ruby-core" <ruby-core@...>

Issue #21618 has been reported by Earlopain (Earlopain _).

15 messages 2025/09/30

[ruby-core:123351] [Ruby Bug#21187] Strings concatenated with `\` getting frozen with literal hashes (PRISM only)

From: "tenderlovemaking (Aaron Patterson) via ruby-core" <ruby-core@...>
Date: 2025-09-30 17:12:04 UTC
List: ruby-core #123351
Issue #21187 has been updated by tenderlovemaking (Aaron Patterson).


@kddnewton any updates, or reproduction issues?  I'm confident I fixed the =
issue OP reported.

----------------------------------------
Bug #21187: Strings concatenated with `\` getting frozen with literal hashe=
s (PRISM only)
https://bugs.ruby-lang.org/issues/21187#change-114722

* Author: LocoDelAssembly (Hern=E1n Pereira)
* Status: Open
* 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: UNKNOWN
----------------------------------------
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 -- [email protected]
 To unsubscribe send an email to [email protected]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.rub=
y-lang.org/


In This Thread