To be complete, the other two "failing while reading" cases in the spec are: (`$` marks the beginning and end of the `source_range`) ```ruby "index operator assignments failing while reading" => <<-RUBY, value = nil ...Eregon (Benoit Daloze)
Regarding failing while reading or writing, here is reading: ```ruby namespace = Module.new begin namespace::NotDefined += 1 rescue => e p e pp e.backtrace_locations[0] pp e.backtrace_locations[0].source_range puts e.backtrace_...Eregon (Benoit Daloze)
I found this via this spec: https://github.com/ruby/spec/blob/0f44fd58585fcdc652da70521ecb753f6fda80f9/core/thread/backtrace/location/source_range_spec.rb#L155-L158 It encodes the current CRuby behavior, but as described above I think t...Eregon (Benoit Daloze)
I don't really understand that constraint here, I think either way on the first Ractor#value that Ractor's heap get absorbed by the receiver Ractor. Whether it's only allowed to call Ractor#value once or multiple times (from the receive...Eregon (Benoit Daloze)
matz (Yukihiro Matsumoto) wrote in #note-18: > Reading `$1` after `e.next` is code people actually write Given that does not work on Ruby 4.0 (3rd snippet of #note-13) and there has been no bug report about that, it seems a strong indic...Eregon (Benoit Daloze)
* https://logs.rubyci.org/osx1400arm/ruby-master/log/20260807T174503Z.fail.html.gz 1) File.setgid? accepts a path in a non-UTF-8, ASCII-compatible encoding containing non-ASCII characters FAILED Expected false == true to be truth...Eregon (Benoit Daloze)