April 2025 - ruby-core - ml.ruby-lang.org

[ruby-core:121592] [Ruby Bug#21256] `it` value is wrapped in an array when that doesn't happen with numbered parameter
by Earlopain (Earlopain _) 18 Jul '25

18 Jul '25

Issue #21256 has been reported by Earlopain (Earlopain _). ---------------------------------------- Bug #21256: `it` value is wrapped in an array when that doesn't happen with numbered parameter https://bugs.ruby-lang.org/issues/21256 * Author: Earlopain (Earlopain _) * Status: Open * ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I have the following script: ```rb require "bundler/inline" gemfile do source "https://rubygems.org" gem "rspec-core", "3.13.3" gem "rspec-expectations", "3.13.3" end require "rspec/autorun" require "rspec/expectations" RSpec::Matchers.define :example do chain(:foo) { pp _1 } chain(:bar) { pp it } end RSpec.describe "demo" do it do example.foo(1) example.bar(2) end end ``` It calls two methods were the only difference is that one accesses the argument with `_1`, the other with `it`. It prints the following: ``` 1 [2] ``` So, `it` for some reason wraps it in an array. I appologise for the reproduction script, it uses `rspec` and the amount of metaprogramming it uses makes it impossible for me to reduce this further. When running with `parser=parse.y`, the expected output is returned (just `2`, no array). I also tested against current ruby-dev and it also happens there. -- https://bugs.ruby-lang.org/

2 4

[ruby-core:112664] [Ruby master Bug#19473] can't be called from trap context (ThreadError) is too limiting
by Eregon (Benoit Daloze) 15 Jul '25

15 Jul '25

Issue #19473 has been reported by Eregon (Benoit Daloze). ---------------------------------------- Bug #19473: can't be called from trap context (ThreadError) is too limiting https://bugs.ruby-lang.org/issues/19473 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Simple reproducer: ``` $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-linux] -e:1:in `synchronize': can't be called from trap context (ThreadError) from -e:1:in `block in <main>' from -e:1:in `kill' from -e:1:in `<main>' ``` Expected behavior: ``` $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' truffleruby 22.3.1, like ruby 3.0.3, GraalVM CE Native [x86_64-linux] :OK $ ruby -ve 'm=Mutex.new; trap(:HUP) { m.synchronize { p :OK } }; Process.kill :HUP, Process.pid; sleep 0.1' jruby 9.4.0.0 (3.1.0) 2022-11-23 95c0ec159f OpenJDK 64-Bit Server VM 17.0.6+10 on 17.0.6+10 +jit [x86_64-linux] :OK ``` This exception is highly problematic, for instance it breaks `Timeout.timeout` in `trap`: https://github.com/ruby/timeout/issues/17#issuecomment-1142035939 I suppose this behavior is because *sometimes* it's problematic to lock a Mutex in trap, e.g., if it's already locked by the main thread/fiber. However, that's just one case, not all, so we should not raise an exception early like that. There seems to be no valid reason to prevent *all* `Mutex#synchronize` in `trap`. After all, if the Mutex for instance is only used in `trap`, it's well-defined AFAIK. For instance a given trap handler does not seem executed concurrently: ``` $ ruby -ve 'trap(:HUP) { puts "in trap\n"+caller.join("\n")+"\n\n"; sleep 0.1 }; pid = Process.pid; Process.wait fork { 20.times { Process.kill :HUP, pid } }; sleep 1' ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-linux] in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' in trap -e:1:in `wait' -e:1:in `<main>' ``` And if the trap handler using the Mutex is never called while the Mutex is held by the main thread/fiber, there is also no problem. -- https://bugs.ruby-lang.org/

8 27

[ruby-core:121721] [Ruby Bug#21283] Some tests of TestMkmfConvertible is failing with VS2022 17.14.0 preview 4.0
by hsbt (Hiroshi SHIBATA) 14 Jul '25

14 Jul '25

Issue #21283 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #21283: Some tests of TestMkmfConvertible is failing with VS2022 17.14.0 preview 4.0 https://bugs.ruby-lang.org/issues/21283 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The following tests are broken with VS2022 17.14.0 preview 4.0. ``` 1) Error: TestMkmfConvertible#test_typeof_typedef: Test::Unit::ProxyError: invalid byte sequence in UTF-8 V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:21:in 'block (2 levels) in TestMkmfConvertible#test_typeof_typedef' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:16:in 'Array#each' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:16:in 'block in TestMkmfConvertible#test_typeof_typedef' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:15:in 'Array#each' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:15:in 'TestMkmfConvertible#test_typeof_typedef' 2) Error: TestMkmfConvertible#test_typeof_builtin: Test::Unit::ProxyError: invalid byte sequence in UTF-8 V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:8:in 'block (2 levels) in TestMkmfConvertible#test_typeof_builtin' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:7:in 'Array#each' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:7:in 'block in TestMkmfConvertible#test_typeof_builtin' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:6:in 'Array#each' V:/github.com/ruby/ruby/test/mkmf/test_convertible.rb:6:in 'TestMkmfConvertible#test_typeof_builtin' ``` They are working fine with VS2019. -- https://bugs.ruby-lang.org/

4 7

[ruby-core:120833] [Ruby master Bug#21099] TestGc#test_gc_stress_at_startup assertion failure
by sanjioh (Fabio Sangiovanni) 14 Jul '25

14 Jul '25

Issue #21099 has been reported by sanjioh (Fabio Sangiovanni). ---------------------------------------- Bug #21099: TestGc#test_gc_stress_at_startup assertion failure https://bugs.ruby-lang.org/issues/21099 * Author: sanjioh (Fabio Sangiovanni) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) +PRISM [x86_64-darwin24] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Hi all, I'm running macOS 15.2, and on my machine the test `TestGc#test_gc_stress_at_startup` results in an assertion failure. These are my current configure flags: ``` ../configure \ --prefix="$SOURCEDIR/ruby_3.4.1" \ --enable-debug-env \ --enable-devel \ cppflags="-DRUBY_DEBUG" \ optflags="-O0 -fno-omit-frame-pointer" ``` make command line for running tests (invoked from the build directory): ``` make test-all TESTS="../test/ruby/test_gc.rb --name=TestGc#test_gc_stress_at_startup" ``` output: ``` Run options: --seed=7555 "--ruby=./miniruby -I../lib -I. -I.ext/common ../tool/runruby.rb --extout=.ext -- --disable-gems" --excludes-dir=../test/.excludes --name=!/memory_leak/ --name=TestGc#test_gc_stress_at_startup # Running tests: [1/1] TestGc#test_gc_stress_at_startup = 3.18 s 1) Failure: TestGc#test_gc_stress_at_startup [/Users/fabio/ruby_xcode/ruby/test/ruby/test_gc.rb:776]: [Bug #15784] pid 16632 killed by SIGABRT (signal 6) | ../gc/default/default.c:1714: Assertion Failed: heap_add_poolpage:page->freelist != NULL | ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) [x86_64-darwin24] | | -- Crash Report log information -------------------------------------------- | See Crash Report log file in one of the following locations: | * ~/Library/Logs/DiagnosticReports | * /Library/Logs/DiagnosticReports | for more details. | Don't forget to include the above Crash Report log file in bug reports. | | -- Control frame information ----------------------------------------------- | c:0001 p:---- s:0003 e:000002 DUMMY [FINISH] | | | -- Threading information --------------------------------------------------- | Total ractor count: 0 | Ruby thread count for this ractor: 0 | | -- C level backtrace information ------------------------------------------- | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace+0x1d) [0x10515014d] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:823 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace) (null):0 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_vm_bugreport+0x2c1) [0x105150431] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:1155 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x156) [0x104e41056] /Users/fabio/ruby_xcode/ruby/build/../error.c:1215 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x0) [0x104e40f00] /Users/fabio/ruby_xcode/ruby/build/../error.c:1191 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure) (null):0 | /Users/fabio/ruby_xcode/ruby/build/ruby(heap_add_poolpage+0xa9) [0x104e84ea9] ../gc/default/default.c:1714 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_step+0x204) [0x104e80224] ../gc/default/default.c:3941 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_rest+0x53) [0x104e7fff3] ../gc/default/default.c:3979 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep+0x98) [0x104e7c418] ../gc/default/default.c:4151 | /Users/fabio/ruby_xcode/ruby/build/ruby(gc_start+0x5f9) [0x104e86159] ../gc/default/default.c:6472 | /Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect+0x2c) [0x104e87bbc] ../gc/default/default.c:6351 | /Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect_with_gvl+0xb4) [0x104e8dbc4] ../gc/default/default.c:6753 | /Users/fabio/ruby_xcode/ruby/build/ruby(objspace_malloc_gc_stress+0x8f) [0x104e8daff] ../gc/default/default.c:7996 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_gc_impl_malloc+0x49) [0x104e8d8f9] ../gc/default/default.c:8207 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2_body+0x32) [0x104e76a82] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4699 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2+0x1d) [0x104e76a3d] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4693 | /Users/fabio/ruby_xcode/ruby/build/ruby(pin_array_list_new+0x6f) [0x10511ab3f] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4389 | /Users/fabio/ruby_xcode/ruby/build/ruby(Init_vm_objects+0x1b) [0x10511aa6b] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4446 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_setup+0x46) [0x104e4f0e6] /Users/fabio/ruby_xcode/ruby/build/../eval.c:82 | /Users/fabio/ruby_xcode/ruby/build/ruby(ruby_init+0xd) [0x104e4f3fd] /Users/fabio/ruby_xcode/ruby/build/../eval.c:98 | /Users/fabio/ruby_xcode/ruby/build/ruby(rb_main+0x2b) [0x104d2e6bb] /Users/fabio/ruby_xcode/ruby/build/../main.c:39 | /Users/fabio/ruby_xcode/ruby/build/ruby(main+0x62) [0x104d2e662] /Users/fabio/ruby_xcode/ruby/build/../main.c:65 | | -- Other runtime information ----------------------------------------------- | | * Process memory map: | | 104d2d000-105308000 r-x /Users/fabio/ruby_xcode/ruby/build/ruby | 105308000-105315000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby | 105315000-105317000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby | 105317000-10532c000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby | 10532c000-105500000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby | 105500000-105502000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105502000-105507000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105507000-105508000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105508000-10550c000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 10550c000-10550d000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 10550d000-105516000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105516000-105517000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105517000-105518000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105518000-105521000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105521000-105522000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105522000-105523000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105523000-105524000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105524000-10552b000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105530000-105540000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 105573000-1055d3000 r-x /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055d3000-1055d7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055d7000-1055db000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055db000-1055e7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib | 1055e7000-105c3e000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby | 105c3e000-106295000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby | 600000000000-600020000000 rw- | 7f9643f00000-7f9644000000 rw- | 7f9644000000-7f9644800000 rw- | 7f9644800000-7f9644900000 rw- | 7f9644900000-7f9644901000 rw- | 7f9644a00000-7f9644b00000 rw- | 7ff7b71d3000-7ff7ba9d3000 --- | 7ff7ba9d3000-7ff7bb1d3000 rw- | 7ff800000000-7ff840000000 r-- | 7ff840000000-7ff844b02000 r-- | 7ff844b02000-7ff844b4a000 r-- | 7ff844b4a000-7ff844c00000 rw- | 7ff844c00000-7ff844e00000 rw- | 7ff844e00000-7ff845000000 rw- | 7ff845000000-7ff845200000 rw- | 7ff845200000-7ff845400000 rw- | 7ff845400000-7ff845600000 rw- | 7ff845600000-7ff880000000 r-- | 7ff880000000-7ffd40000000 r-- | 7ffd40000000-7ffd44400000 r-- | 7ffd44400000-7ffd44600000 rw- | 7ffd44600000-7ffd44800000 rw- | 7ffd44800000-7ffd80000000 r-- | 7ffd80000000-7ffffe000000 r-- | 7fffffe00000-7fffffe01000 r-- | 7ffffffad000-7ffffffae000 r-x | [IMPORTANT] | Don't forget to include the Crash Report log file under | DiagnosticReports directory in bug reports. | . 1. [2/3] Assertion for "stderr" | <[]> expected but was | <["../gc/default/default.c:1714: Assertion Failed: heap_add_poolpage:page->freelist != NULL", | "ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) [x86_64-darwin24]", | "", | "-- Crash Report log information --------------------------------------------", | " See Crash Report log file in one of the following locations:", | " * ~/Library/Logs/DiagnosticReports", | " * /Library/Logs/DiagnosticReports", | " for more details.", | "Don't forget to include the above Crash Report log file in bug reports.", | "", | "-- Control frame information -----------------------------------------------", | "c:0001 p:---- s:0003 e:000002 DUMMY [FINISH]", | "", | "", | "-- Threading information ---------------------------------------------------", | "Total ractor count: 0", | "Ruby thread count for this ractor: 0", | "", | "-- C level backtrace information -------------------------------------------", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace+0x1d) [0x10515014d] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:823", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_print_backtrace) (null):0", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_vm_bugreport+0x2c1) [0x105150431] /Users/fabio/ruby_xcode/ruby/build/../vm_dump.c:1155", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x156) [0x104e41056] /Users/fabio/ruby_xcode/ruby/build/../error.c:1215", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure_detail+0x0) [0x104e40f00] /Users/fabio/ruby_xcode/ruby/build/../error.c:1191", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_assert_failure) (null):0", | "/Users/fabio/ruby_xcode/ruby/build/ruby(heap_add_poolpage+0xa9) [0x104e84ea9] ../gc/default/default.c:1714", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_step+0x204) [0x104e80224] ../gc/default/default.c:3941", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep_rest+0x53) [0x104e7fff3] ../gc/default/default.c:3979", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_sweep+0x98) [0x104e7c418] ../gc/default/default.c:4151", | "/Users/fabio/ruby_xcode/ruby/build/ruby(gc_start+0x5f9) [0x104e86159] ../gc/default/default.c:6472", | "/Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect+0x2c) [0x104e87bbc] ../gc/default/default.c:6351", | "/Users/fabio/ruby_xcode/ruby/build/ruby(garbage_collect_with_gvl+0xb4) [0x104e8dbc4] ../gc/default/default.c:6753", | "/Users/fabio/ruby_xcode/ruby/build/ruby(objspace_malloc_gc_stress+0x8f) [0x104e8daff] ../gc/default/default.c:7996", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_gc_impl_malloc+0x49) [0x104e8d8f9] ../gc/default/default.c:8207", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2_body+0x32) [0x104e76a82] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4699", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_xmalloc2+0x1d) [0x104e76a3d] /Users/fabio/ruby_xcode/ruby/build/../gc.c:4693", | "/Users/fabio/ruby_xcode/ruby/build/ruby(pin_array_list_new+0x6f) [0x10511ab3f] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4389", | "/Users/fabio/ruby_xcode/ruby/build/ruby(Init_vm_objects+0x1b) [0x10511aa6b] /Users/fabio/ruby_xcode/ruby/build/../vm.c:4446", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_setup+0x46) [0x104e4f0e6] /Users/fabio/ruby_xcode/ruby/build/../eval.c:82", | "/Users/fabio/ruby_xcode/ruby/build/ruby(ruby_init+0xd) [0x104e4f3fd] /Users/fabio/ruby_xcode/ruby/build/../eval.c:98", | "/Users/fabio/ruby_xcode/ruby/build/ruby(rb_main+0x2b) [0x104d2e6bb] /Users/fabio/ruby_xcode/ruby/build/../main.c:39", | "/Users/fabio/ruby_xcode/ruby/build/ruby(main+0x62) [0x104d2e662] /Users/fabio/ruby_xcode/ruby/build/../main.c:65", | "", | "-- Other runtime information -----------------------------------------------", | "", | "* Process memory map:", | "", | "104d2d000-105308000 r-x /Users/fabio/ruby_xcode/ruby/build/ruby", | "105308000-105315000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105315000-105317000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105317000-10532c000 rw- /Users/fabio/ruby_xcode/ruby/build/ruby", | "10532c000-105500000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby", | "105500000-105502000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105502000-105507000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105507000-105508000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105508000-10550c000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "10550c000-10550d000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "10550d000-105516000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105516000-105517000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105517000-105518000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105518000-105521000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105521000-105522000 --- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105522000-105523000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105523000-105524000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105524000-10552b000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105530000-105540000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "105573000-1055d3000 r-x /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055d3000-1055d7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055d7000-1055db000 rw- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055db000-1055e7000 r-- /usr/local/Cellar/gmp/6.3.0/lib/libgmp.10.dylib", | "1055e7000-105c3e000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby", | "105c3e000-106295000 r-- /Users/fabio/ruby_xcode/ruby/build/ruby.dSYM/Contents/Resources/DWARF/ruby", | "600000000000-600020000000 rw-", | "7f9643f00000-7f9644000000 rw-", | "7f9644000000-7f9644800000 rw-", | "7f9644800000-7f9644900000 rw-", | "7f9644900000-7f9644901000 rw-", | "7f9644a00000-7f9644b00000 rw-", | "7ff7b71d3000-7ff7ba9d3000 ---", | "7ff7ba9d3000-7ff7bb1d3000 rw-", | "7ff800000000-7ff840000000 r--", | "7ff840000000-7ff844b02000 r--", | "7ff844b02000-7ff844b4a000 r--", | "7ff844b4a000-7ff844c00000 rw-", | "7ff844c00000-7ff844e00000 rw-", | "7ff844e00000-7ff845000000 rw-", | "7ff845000000-7ff845200000 rw-", | "7ff845200000-7ff845400000 rw-", | "7ff845400000-7ff845600000 rw-", | "7ff845600000-7ff880000000 r--", | "7ff880000000-7ffd40000000 r--", | "7ffd40000000-7ffd44400000 r--", | "7ffd44400000-7ffd44600000 rw-", | "7ffd44600000-7ffd44800000 rw-", | "7ffd44800000-7ffd80000000 r--", | "7ffd80000000-7ffffe000000 r--", | "7fffffe00000-7fffffe01000 r--", | "7ffffffad000-7ffffffae000 r-x", | "[IMPORTANT]", | "Don't forget to include the Crash Report log file under", | "DiagnosticReports directory in bug reports.", | ""]>. 2. [3/3] Assertion for "success?" | Expected #<Process::Status: pid 16632 SIGABRT (signal 6)> to be success?. Finished tests in 3.208725s, 0.3117 tests/s, 1.8699 assertions/s. 1 tests, 6 assertions, 1 failures, 0 errors, 0 skips ruby -v: ruby 3.5.0dev (2025-01-29T15:16:47Z master d3bb42776c) +PRISM [x86_64-darwin24] make: *** [uncommon.mk:965: yes-test-all] Error 1 ``` -- https://bugs.ruby-lang.org/

3 3

[ruby-core:121437] [Ruby Bug#21197] Prism does not accept newline after defined? keyword
by kddnewton (Kevin Newton) 14 Jul '25

14 Jul '25

Issue #21197 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Bug #21197: Prism does not accept newline after defined? keyword https://bugs.ruby-lang.org/issues/21197 * Author: kddnewton (Kevin Newton) * Status: Open * Assignee: prism * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ``` defined? (1) ``` -- https://bugs.ruby-lang.org/

2 3

[ruby-core:120618] [Ruby master Bug#21029] Prism behavior for `defined? (;x)` differs
by qnighy (Masaki Hara) 14 Jul '25

14 Jul '25

Issue #21029 has been reported by qnighy (Masaki Hara). ---------------------------------------- Bug #21029: Prism behavior for `defined? (;x)` differs https://bugs.ruby-lang.org/issues/21029 * Author: qnighy (Masaki Hara) * Status: Open * ruby -v: ruby 3.5.0dev (2025-01-11T03:21:57Z master 1b3037081e) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism has a different behavior for `(;expr)` when used in `defined?` predicate: ```console % ./miniruby --parser=prism -e "p defined? (;x)" nil % ./miniruby --parser=parse.y -e "p defined? (;x)" "expression" ``` Although not a significant difference, aligning either of them with the other would be better. -- https://bugs.ruby-lang.org/

5 11

[ruby-core:111027] [Ruby master Bug#19154] Specify require and autoload guarantees in ractors
by fxn (Xavier Noria) 14 Jul '25

14 Jul '25

Issue #19154 has been reported by fxn (Xavier Noria). ---------------------------------------- Bug #19154: Specify require and autoload guarantees in ractors https://bugs.ruby-lang.org/issues/19154 * Author: fxn (Xavier Noria) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0preview3 (2022-11-27) [x86_64-darwin22] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Given a file `c.rb`: ```ruby class C end ``` the following script: ```ruby r1 = Ractor.new do require './c.rb' end r2 = Ractor.new do require './c.rb' end r1.take r2.take ``` raises: ``` % ruby -v foo.rb ruby 3.2.0preview3 (2022-11-27) [x86_64-darwin22] foo.rb:1: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues. #<Thread:0x000000010fee2928 run> terminated with exception (report_on_exception is true): #<Thread:0x00000001102acfe0 run> terminated with exception (report_on_exception is true): <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' from foo.rb:6:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require'<internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': : can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' from foo.rb:6:in `block in <main>' <internal:ractor>:698:in `take': thrown by remote Ractor. (Ractor::RemoteError) from foo.rb:9:in `<main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:164:in `ensure in require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:167:in `require' from foo.rb:2:in `block in <main>' <internal:/Users/fxn/.rbenv/versions/3.2.0-preview3/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:37:in `require': can not access non-shareable objects in constant Kernel::RUBYGEMS_ACTIVATION_MONITOR by non-main ractor. (Ractor::IsolationError) from foo.rb:2:in `block in <main>' ``` Would it be possible to have documentation about their interaction? This is important also to understand autoloading within ractors, since constant references may trigger `require` calls. -- https://bugs.ruby-lang.org/

5 13

[ruby-core:116382] [Ruby master Feature#20205] Enable `frozen_string_literal` by default
by byroot (Jean Boussier) 10 Jul '25

10 Jul '25

Issue #20205 has been reported by byroot (Jean Boussier). ---------------------------------------- Feature #20205: Enable `frozen_string_literal` by default https://bugs.ruby-lang.org/issues/20205 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal ---------------------------------------- ### Context The `frozen_string_literal: true` pragma was introduced in Ruby 2.3, and as far as I'm aware the plan was initially to make it the default for Ruby 3.0, but this plan was abandoned because it would be too much of a breaking change without any real further notice. According to Matz, he still wishes to enable `frozen_string_literal` by default in the future, but a reasonable migration plan is required. The main issue is backward compatibility, flipping the switch immediately would break a lot of code, so there must be some deprecation period. The usual the path forward for this kind of change is to emit deprecation warnings one of multiple versions in advance. One example of that was the Ruby 2.7 keyword argument deprecation. It was quite verbose, and some users were initially annoyed, but I think the community pulled through it and I don't seem to hear much about it anymore. So for frozen string literals, the first step would be to start warning when a string that would be frozen in the future is mutated. ### Deprecation Warning Implementation I implemented a quick proof of concept with @etienne in https://github.com/Shopify/ruby/pull/549 In short: - Files with `# frozen_string_literal: true` or `# frozen_string_literal: false` don't change in behavior at all. - Files with no `# frozen_string_literal` comment are compiled to use `putchilledstring` opcode instead of regular `putstring`. - This opcode mark the string with a user flag, when these strings are mutated, a warning is issued. Currently the proof of concept issue the warning at the mutation location, which in some case can make locating where the string was allocated a bit hard. But it is possible to improve it so the message also include the location at which the literal string was allocated, and learning from the keyword argument warning experience, we can record which warnings were already issued to avoid spamming users with duplicated warnings. As currently implemented, there is almost no overhead. If we modify the implementation to record the literal location, we'd incur a small memory overhead for each literal string in a file without an explicit `frozen_string_literal` pragma. But I believe we could do it in a way that has no overhead if `Warning[:deprecated] = false`. ### Timeline The migration would happen in 3 steps, each step can potentially last multiple releases. e.g. `R0` could be `3.4`, `R1` be `3.7` and `R2` be `4.0`. I don't have a strong opinion on the pace. - Release `R0`: introduce the deprecation warning (only if deprecation warnings enabled). - Release `R1`: make the deprecation warning show up regardless of verbosity level. - Release `R2`: make string literals frozen by default. ### Impact Given that `rubocop` is quite popular in the community and it has enforced the usage of `# frozen_string_literal: true` for years now, I suspect a large part of the actively maintained codebases in the wild wouldn't see any warnings. And with recent versions of `minitest` enabling deprecation warnings by default (and [potentially RSpec too](https://github.com/rspec/rspec-core/issues/2867)) the few that didn't migrate will likely be made compatible quickly. The real problem of course are the less actively developed libraries and applications. For such cases, any codebase can remain compatible by setting `RUBYOPT="--disable=frozen_string_literal"`, and so even after `R2` release. The flag would never be removed any legacy codebase can continue upgrading Ruby without changing a single line of cod by just flipping this flag. ### Workflow for library maintainers As a library maintainer, fixing the deprecation warnings can be as simple as prepending `# frozen_string_literal: false` at the top of all their source files, and this will keep working forever. Alternatively they can of course make their code compatible with frozen string literals. Code that is frozen string literal compatible doesn't need to explicitly declare it. Only code that need it turned of need to do so. ### Workflow for application owners For application owners, the workflow is the same than for libraries. However if they depend on a gem that hasn't updated, or that they can't upgrade it, they can run their application with `RUBYOPT="--disable=frozen_string_literal"` and it will keep working forever. Any user running into an incompatibility issue can set `RUBYOPT="--disable=frozen_string_literal"` forever, even in `4.x`, the only thing changing is the default value. And any application for which all dependencies have been made fully frozen string literal compatible can set `RUBYOPT="--enable=frozen_string_literal"` and start immediately removing magic comment from their codebase. -- https://bugs.ruby-lang.org/

20 73

[ruby-core:121621] [Ruby Feature#21262] Proposal: `Ractor::Port`
by ko1 (Koichi Sasada) 08 Jul '25

08 Jul '25

Issue #21262 has been reported by ko1 (Koichi Sasada). ---------------------------------------- Feature #21262: Proposal: `Ractor::Port` https://bugs.ruby-lang.org/issues/21262 * Author: ko1 (Koichi Sasada) * Status: Assigned * Assignee: ko1 (Koichi Sasada) * Target version: 3.5 ---------------------------------------- # Proposal: `Ractor::Port` In concurrent Ruby applications using Ractors, safely and efficiently communicating results between Ractors is a common challenge. We propose `Ractor::Port` as a lightweight, safe, and ergonomic abstraction to simplify communication patterns, especially in request-response models. ```ruby # usage example port = Ractor::Port.new Ractor.new port do |port| port << 42 port << 43 end # Success: wait for sending port.receive #=> 42 Ractor.new port do |port| port.receive # Error: only the creator Ractor can receive from this port. end port.receive #=> 43 ``` This is a similar concept to ["Channel"](https://bugs.ruby-lang.org/issues/21121), but it is tightly coupled with the creator Ractor and no other Ractors can receive anything from that port. In that sense, it is conceptually closer to a socket file descriptor (e.g., a destination and port number pair in TCP/IP). We can implement `Port` with `Ractor.receive_if` like this: ```ruby class Ractor::Port def initialize @r = Ractor.current @tag = genid() end def send obj @r << [@tag, obj] end def receive raise unless @r == Ractor.current Ractor.receive_if do |(tag, result) if tag == @tag return result end end end end ``` With `Ractor::Port`, we can deprecate `Ractor.receive_if`, `Ractor.yield`, and `Ractor#take`. Ports act as clear, self-contained endpoints for message passing, which makes these older primitives redundant. Furthermore, Port-based communication is significantly easier to implement and reason about—especially when considering synchronization challenges around `Ractor.select` and rendezvous semantics. ## Background: Limitations of current communication patterns Let's discuss how to make server-like service ractors. ### No response server We can make server-like Ractors like this: ```ruby # EX1 def fib(n) = n > 1 : fib(n-2) + fib(n-1) : 1 # A ractor calculate fib(n) fib_srv = Ractor.new do while true param = Ractor.receive result = fib(param) end end fib_srv << 10 ``` In this case, the main Ractor requests `fib_srv` to calculate `fib(10)`. However, currently, there is no way to retrieve the result. ### Return value to the sender ractor There are several possible approaches. First, we can send the sender Ractor along with the parameter, and ask the server to send the result back to the sender. ```ruby # EX2 fib_srv = Ractor.new do while true param, sender = Ractor.receive result = fib(param) sender << result end end fib_srv << [10, Ractor.current] do_some_work() Ractor.receive #=> fib(10) ``` This approach works well in simple cases. However, with EX2, handling multiple concurrent responses becomes difficult. The results are pushed into the same mailbox, and since `Ractor.receive` retrieves messages without discriminating the source, it's unclear which server returned which result. ```ruby # EX3 def fact(n) = n > 1 : fact(n-1) * n fib_srv = Ractor.new do while true param, sender = Ractor.receive result = fib(param) sender << result end end fact_srv = Ractor.new do while true param, sender = Ractor.receive result = fact(param) sender << result end end fib_srv << [10, Ractor.current] fib_srv << [20, Ractor.current] fact_srv << [10, Ractor.current] fact_srv << [20, Ractor.current] do_some_work() Ractor.receive #=> fib(10) or fact(10), which? # If the servers uses Ractors more (calculate them in parallel), # fib(20) and fact(20) can be returned. ``` Because `Ractor.receive` retrieves all messages indiscriminately, developers must add their own tagging logic to distinguish results. While tagging (as shown in EX4) helps, it introduces additional complexity and brittleness. ### Responses with request ID The following code returns a result with request id (a pair of the name of server and a parameter). ```ruby # EX4 fib_srv = Ractor.new do while true param, sender = Ractor.receive result = fib(param) sender << [[:fib, param], result] end end fact_srv = Ractor.new do while true param, sender = Ractor.receive result = fact(param) sender << [[:fact, param], result] end end do_some_work() fib_srv << [10, Ractor.current] fib_srv << [20, Ractor.current] fact_srv << [10, Ractor.current] fact_srv << [20, Ractor.current] Ractor.receive_if do |id, result| case id in [:fib, n] p "fib(#{n}) = #{result}" in [:fact, n] p "fact(#{n}) = #{result}" end end # or if you want to use specific results, like: p fib20: Ractor.receive_if{|id, result| id => [:fib, 20]; result} p fact10: Ractor.receive_if{|id, result| id => [:fact, 10]; result} p fact20: Ractor.receive_if{|id, result| id => [:fact, 20]; result} p fib10: Ractor.receive_if{|id, result| id => [:fib, 10]; result} ``` This approach closely resembles pattern matching in Erlang or Elixir, where responses are tagged and matched structurally. However, this solution still has an issue: if `do_some_work()` uses `Ractor.receive`, it may accidentally consume any message. In other words, `Ractor.receive` can only be safely used when you're certain that no other code is using it. (Another trivial issue is, different servers can return same identity, like `[:fact, num]` returned by NewsPaper server. It is confusing). ### Using channels To solve this issue, we can make a channel with different Ractors. Channels can be implemented using Ractors, as illustrated below. ```ruby # EX5 # Servers are completely same to EX3 fib_srv = Ractor.new do while true param, sender = Ractor.receive result = fib(param) sender << result end end fact_srv = Ractor.new do while true param, sender = Ractor.receive result = fact(param) sender << result end end # Create a new channel using a Ractor def new_channel Ractor.new do while true Ractor.yield Ractor.receive end end end fib_srv << [10, fib10_ch = new_channel] fib_srv << [20, fib20_ch = new_channel] fact_srv << [10, fact10_ch = new_channel] fact_srv << [20, fact20_ch = new_channel] do_something() p fib20: fib20_ch.take # wait for fib(20) p fact10: fact10_ch.take # wait for fact(10) p fib10: fib10_ch.take # wait for fib(10) p fact20: fact10_ch.take # wait for fact(20) # or chs = [fib10_ch, fib20_ch, fact10_ch, fact20_ch] while !chs.empty? ch, result = Ractor.select(*chs) # wait for multiple channels p ch, result chs.delete ch end ``` Channel approach solves the issue of EX4. The above implementation introduce some overhead to create channel ractors, but we can introduce special implementation to reduce this Ractor creation overhead. However, in the Actor model, the communication pattern is to send a message to a specific actor. In contrast, channels are used to send messages through a shared conduit, without caring which receiver (if any) handles the message. Also, channels can have some overhead, as discussed below. ### Summary of background Currently, when implementing request-response patterns with Ractors, developers face challenges in tracking results, managing identifiers, and avoiding message conflicts. Existing primitives like `receive_if`, `take`, or channels implemented with Ractors are either error-prone or inefficient. ## Proposal Introduce `Ractor::Port` as an alternative to channels. It is a natural extension of the Actor model. In fact, it is thin wrapper of current send/receive model as illustrated at the top of this proposal. With the `Ractor::Port`, we can rewrite above examples with it. ```ruby # EX6 # Completely same as EX3's servers fib_srv = Ractor.new do while true param, sender = Ractor.receive result = fib(param) sender << result end end fact_srv = Ractor.new do while true param, sender = Ractor.receive result = fact(param) sender << result end end fib_srv << [10, fib10_port = Ractor::Port.new] fib_srv << [20, fib20_port = Ractor::Port.new] fact_srv << [10, fact10_port = Ractor::Port.new] fact_srv << [20, fact20_port = Ractor::Port.new] do_something p fib10_port.receive #=> fib(10) p fib20_port.receive #=> fib(20) p fact10_port.receive #=> fact(10) p fact20_port.receive #=> fact(20) # or ports = [fib10_port, fib20_port, fact10_port, fact20_port] while !ports.empty? port, result = Ractor.select(*ports) case port when fib10_port p fib10: result ... else raise "This should not happen (BUG)." end ports.delete(port) end ``` `Ractor::Port` resolves key pain points in message passing between Ractors: * It guarantees that incoming messages are only delivered to the intended Ractor, preventing tag collisions. * It enables message routing without relying on global receive blocks (`Ractor.receive`), which are prone to unintended consumption. * It replaces more complex primitives like `.receive_if`, `.yield`, and `#take` with a simpler, composable abstraction. * It maps cleanly to the Actor model semantics Ruby intends to support with Ractors. While the pattern looks similar to using channels, the semantics and guarantees are different in meaningful ways. The advantages of using Ports include: * Safer than channels in practice * When using a Port, if `#send` succeeds, it means the destination Ractor is still alive (i.e., it's running). * In contrast, with a channel, there's no guarantee that any Ractor is still available to receive from it. * Of course, even with a port, there's no guarantee that the destination Ractor will actually process the message — it might ignore it. * But at least you don't need to worry about the Ractor having already terminated unexpectedly. * In other words, using a port eliminates one major failure case, making the communication model more predictable. * This is one of the reasons why Ruby went with the "Actor" model (hence the name Ractor), instead of the "CSP" model. * Faster than channels in both creation and message transmission * When creating a channel, we need to prepare a container data structure. When creating a port, it is lightweight data (a pair of Ractor and newly created ID). * On the channel transmission, we need copying a data to channel and a copying to the receiving ractor. On the port, it only needs to copy from the src ractor to the dst ractor. This issue becomes more significant due to Ractor-local garbage collection and isolation of object spaces. * Easy to implement. We only need to implement `Port#receive` to synchronize with other ractors. * `#send/.receive` is easy to implement because we only need to lock the receiving ractor. * `.yield/#take` is not easy to implement because we need to lock taking and receiving ractors because it is rendezvous style synchronization. * `.select` is DIFFICULT to support current spec. Now CI doesn't stable yet. * A simpler spec reduces bugs, and maybe leads to faster implementation. Disadvantages: 1. It is not a well-known concept, especially for Go language users. 2. We need additional abstraction like producer(s)-consumer(s) concurrent applications. For (2), I want to introduce an example code. We can write a 1-producer, multiple-consumer pattern with a channel. ```ruby # channel version of 1 producer & consumers ch = new_channel RN = 10 # make 10 consumers consumers = RN.times.map do Ractor.new ch do while param = ch.receive task(param) end end end tasks.each do |task| ch << task end ``` With Port, we need to introduce a load balancing mechanism: ```ruby # Port version of 1 producer & consumers control_port = Ractor::Port.new consumers = RN.times.map do Ractor.new control_port control_port do |control_port| while true control_port << [:ready, Ractor.current] # register - ready param = Ractor.receive # it assumes task doesn't use Ractor.receive task(param) end end end tasks.each do |task| control_port.receive => [:ready, consumer] # send a task to a ready consumer consumer << task end ``` Of course we can make a library for that (like OTP on Erlang). ### Default port of Ractors Each Ractor has a default port and `Ractor#send` is equal to `Ractor.current.default_port#send`. Of course, `Ractor.receive` is equal to `Ractor.current.default_port.receive`. For the simple case, we can keep to use `Ractor#send` and `Ractor.receive` ### Deprecation of Ractor#take and Ractor.yield With the Port concept, we can focus solely on send and receive—that is, direct manipulation of a Ractor’s mailbox. Ports provide a clean and functional alternative to `Ractor#take` and `Ractor.yield`, making them unnecessary in most use cases. Moreover, Ports are significantly easier to implement, as they require only locking the receiving Ractor, while yield/take involve complex rendezvous-style synchronization. By removing these primitives, we can simplify the specification and reduce implementation complexity—especially around features like `Ractor.select`, which are notoriously hard to get right. ### `Ractor.select` with ports We should wait for multiple port simultaneously so `Ractor.select()` should accept ports. Now `Ractor.select()` can also receiving and yielding the value, but if we remove the `#take` functionality, `Ractor.select` only need to support ports. ### Wait for termination `Ractor#take` is designed from an idea of getting termination result (like `Thread#value`). For this purpose, we can introduce `Ractor#join` or `Ractor#value` like Threads or we can keep the name `Ractor#take` for this purpose. We can make `Ractor#join` as a following pseudo-code: ```ruby class Ractor def join # wait for the termination register_termination_port port = Port.new port.receive end # when this ractor terminates, send a message to the registered port def monitor port @monitor_port = port end private def atexit @monitor_port << termination_message end end # there are some questions. # * can we register multiple ports? # * should we support `#join` and `#value` like threads? # or should we support only `#join` to return the value? # * or keep this name as `#take`? Ractor.new do 42 end.join #=> 42 (or true?) ``` It is very similar to `monitor` in Erlang or Elixir. We can also make a supervisor in Erlang like that: ```ruby sv_port = Ractor::Port.new rs = N.times.map do Ractor.new do do_something() end.monitor sv_port end while termination_notice = sv_port.receive p termination_notice end # With Ractor#take, we can write similar code if there is no Ractor.yield rs = N.times.map do Ractor.new do do_something() end end while r, msg = Ractor.select(*rs) p [r, msg] end ``` ## Discussion ### `send` with tag (symbols) If we force users to send a tagged message every time, we can achieve the same effect as Port concept, because a Port can be thought of as a combination of a tag and a destination Ractor. ```ruby r = Ractor.new do loop do tag, msg = Ractor.receive # return 2 values case tag when :TAG p [tag, msg] else # ignore end end end r.send :TAG, 42 r.send :TAGE, 84 # this typo and the message is silently ignored ``` However it has two issues: * If we make a typo in tag name, the message will be silently ignored. * The tag name may conflict with unrelated codes (libraries) ### `Ractor.yield` and `Ractor#take` with channel ractor If we want to leave the `.yield` and `#take`, we can emulate them with channel ractor. ```ruby class Ractor def initialize @yield_ractor = Ractor.new do takers = [] while tag, msg = Ractor.receive case tag when :register @takers << msg when :unregister @takers.delete msg when :yield @takers.pop << msg end end end end def self.yield obj @yield_ractor << [:yield, obj] end def take @yield_ractor << [:register, port = Ractor::Port.new] port.receive ensure @yield_ractor << [:unregister, port] end end ``` ### Opening and closing the port This proposal doesn't contain opening and closing the port, but we can discuss about it. To introduce this attribute, we need to manage which ports (tags) are opening. ## Implementation Now the native implementation is not finished, but we can implement it using the `Ractor.receive_if` mechanism, so we estimate that only a few weeks of work are needed to complete it. ## Summary This proposal introduces the following features and deprecations. * `Ractor::Port` * `Port#send(msg)` – sends a message to the creator of the port. * `Port#receive` – receives a message from the port. * A port is a lightweight data structure (a pair of a Ractor and a tag). * `Ractor#join` or `Ractor#value` – to wait for Ractor termination (like `Thread#join`) * `Ractor#monitor` – to observe when another Ractor terminates * Deprecations: * `Ractor#take` * `Ractor.yield` * `Ractor.receive_if` Thank you for reading this long proposal. If you have any use cases that cannot be addressed with `Ractor::Port`, I'd love to hear them. P.S. Thanks to mame for reviewing this proposal and suggesting that I use ChatGPT to improve the writing. -- https://bugs.ruby-lang.org/

2 7

[ruby-core:117392] [Ruby master Feature#20405] Inline comments
by nobu (Nobuyoshi Nakada) 08 Jul '25

08 Jul '25

Issue #20405 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Feature #20405: Inline comments https://bugs.ruby-lang.org/issues/20405 * Author: nobu (Nobuyoshi Nakada) * Status: Open ---------------------------------------- I propose a new inline comment syntax. ```ruby p (| This is a comment (| and nested one |) /:|) (:|) #=> :| ``` -- https://bugs.ruby-lang.org/

7 10