Benoit Daloze

Results 1300 comments of Benoit Daloze

Some overlap with https://github.com/Shopify/rbi/pull/297

From https://github.com/eregon/actions-shell/actions/runs/9318186931/job/25650009861, `arm64` is used in `ruby -v`, `RUBY_PLATFORM` and RbConfig (except `build` and `build_cpu` which are `aarch64`, but I think we don't have those in TruffleRuby anyway).

Could you share a reproducer we can run? It's very difficult to diagnose this without being able to run it. Note also that the JVM (and Native Image too BTW)...

It's because of https://github.com/banister/method_source/blob/06f21c66380c64ff05c8031c0208eef240da0e83/lib/method_source/code_helpers.rb#L125-L131 And we get different SyntaxError messages with Prism. I checked and CRuby with `RUBYOPT=--parser=prism` has similar errors, so I filed https://github.com/ruby/prism/issues/2734 https://github.com/banister/method_source/blob/06f21c66380c64ff05c8031c0208eef240da0e83/lib/method_source/source_location.rb#L44 makes me want to...

Re benchmarking, see https://twitter.com/eregontp/status/1783444486124638251 / https://gist.github.com/eregon/8e104d291ca64d0834b580d18b837059#file-results-txt

`method_source` is depended on by a bunch of repos and gems: https://github.com/banister/method_source/network/dependents So it seems worth implementing `Method#source` directly in TruffleRuby. OTOH I don't see immediately a popular gem using...

Do you have `JT_SPECS_COMPILATION` or `JT_SPECS_SPLITTING` set in the environment maybe? These specs do seem to pass fine in our darwin-aarch64 CI.

OK, that's kind of expected then since `JT_SPECS_COMPILATION=false` does `--engine.Splitting=false` (unless `JT_SPECS_SPLITTING=true`). So we should check that condition in the `guard` then. Ideally we would check specifically that splitting is...

TruffleRuby does not yet implement Ruby 3.3 features, and that's why there is also no Ruby 3.3 issue yet (it will be created when work starts on it). TruffleRuby does...

> It would be more progressive to prepare a tracker soon to link in the docs (this or future PR). That could be done, OTOH it's significantly easier to contribute...