@tikkss I think there is an issue with your accounting of memory because it doesn't match the RSS of the worker process. This is running your example as-is. ``` $ ruby -v ruby 4.0.2 (2026-03-17 revision d3da9fec82) +PRISM [x86_64-linux]...Eregon (Benoit Daloze)
Eregon (Benoit Daloze) wrote in #note-10: > I'm not sure if [@matz (Yukihiro Matsumoto)](/users/13) made his mind on: Start position: from the `p` of `proc`? Or from the `{`? I confirmed with both @mame and @matz, and matz said it sh...Eregon (Benoit Daloze)
For ```ruby l = -> x, y { x + y } l.call(1) ``` ErrorHighlight shows: ``` test.rb:1:in 'block in <main>': wrong number of arguments (given 1, expected 2) (ArgumentError) caller: test.rb:5 | l.call(1) ^^^^...Eregon (Benoit Daloze)
I was curious what's the reported location for `ArgumentError`s caused by lambda parameters and how ErrorHighlight highlights them. For ```ruby l = lambda { |x, y| x + y } l.call(1) ``` With `parse.y`, the node (`RubyVM::...Eregon (Benoit Daloze)
* In file included from /usr/include/string.h:535, from include/prism/internal/arena.h:12, from src/prism.c:6: In function 'memset', inlined from 'lex_mode_push_regexp' at src/prism.c:290:5: .../...Eregon (Benoit Daloze)
kddnewton (Kevin Newton) wrote in #note-21: > If, regardless, you would like to keep pursuing it, you need to produce working code for those two examples. Done: https://github.com/eregon/error_highlight/pull/1 https://github.com/er...Eregon (Benoit Daloze)
kddnewton (Kevin Newton) wrote in #note-23: > Unless you're once again suggesting we only rely on line/column, which as already mentioned multiple times and rejected multiple times, won't work. Do you have a concrete example why it w...Eregon (Benoit Daloze)
tikkss (Tsutomu Katsube) wrote in #note-1: > You might argue, "Why not run it in a multi-process?" However, > ... Did you measure the difference in memory usage? I'd expect it to be small because each Ruby::Box has pretty much a cop...Eregon (Benoit Daloze)