General

Profile

Eregon (Benoit Daloze)

  • Login: Eregon
  • Registered on: 07/30/2009
  • Last sign in: 10/05/2026

Issues

open closed Total
Assigned issues 2 72 74
Reported issues 29 209 238

Projects

Project Roles Registered on
Ruby Committer 08/02/2012

Activity

10/09/2026

07:26 PM Ruby Revision 477555ee (git): Move efficient_extensions.md under doc/
* It's for any native extension, not just extensions in CRuby, like doc/extension.rdoc. Eregon (Benoit Daloze)
07:26 PM Ruby Revision 49bfc6cd (git): Link to efficient_extensions.md from extension.rdoc for discoverability
Eregon (Benoit Daloze)
07:26 PM Ruby Revision 5ee67ca3 (git): Fix some typos in extension.rdoc
Eregon (Benoit Daloze)
07:26 PM Ruby Revision ef83236c (git): Rework the RUBY_TYPED_FROZEN_SHAREABLE to be more precise and accurate
* See https://github.com/ruby/ruby/pull/18492#discussion_r4207898351 Eregon (Benoit Daloze)
09:59 AM Ruby Feature #22274: Make `IO::Buffer` no longer experimental.
There have been new methods/classes in the last week like:
`IO::Buffer#advance` https://github.com/ruby/ruby/pull/19122
`Introduce IO::Buffer::Storage and parent-relative slice views` https://github.com/ruby/ruby/pull/19186
I thin...
Eregon (Benoit Daloze)

10/08/2026

12:15 PM Ruby Bug #22396: Using rb_postponed_job_trigger causes YJIT/ZJIT compiled methods side exits
I think maybe the bigger issue here is that profiling a program using YJIT or ZJIT might give very misleading results, because the action of profiling itself (if the profiler uses postponed jobs and many do) has the unexpected side effec... Eregon (Benoit Daloze)
12:10 PM Ruby Bug #22396: Using rb_postponed_job_trigger causes YJIT/ZJIT compiled methods side exits
Draft of a potential fix: https://github.com/ruby/ruby/pull/18205
I have tried several things to avoid overhead on the the no-interrupt-path but they mostly failed, I guess the YJIT backend doesn't really support generating code with ...
Eregon (Benoit Daloze)
09:59 AM Ruby Feature #22379: Remove prism mismatch warning from `#syntax_tree`
Two more thoughts on this:
1. Should there be a `version:` keyword argument for `Ruby::Prism.parse(code, version:)`? Because the point of Ruby::Prism is to use the current version always. The default is actually `"latest"`, which by c...
Eregon (Benoit Daloze)

10/07/2026

10:43 PM Ruby Feature #22379: Remove prism mismatch warning from `#syntax_tree`
Overall I think this is a great solution for making `#syntax_tree` reliable.
I asked Claude to think about the consequences of introducing `Ruby::Prism`:
---
It recreates the `ripper` / `parser` gem split. Code that parses the running...
Eregon (Benoit Daloze)
09:12 PM Ruby Feature #22379: Remove prism mismatch warning from `#syntax_tree`
I asked Claude about those questions.
Re the 2 Prism C extensions, it's a non-issue because only `Init_prism` could conflict, and the interpreter resolves its `Init_prism` at link time, and the extension's init is resolved by `dlsym(exte...
Eregon (Benoit Daloze)

Also available in: Atom