Issue #22221 has been updated by Eregon (Benoit Daloze). * [Feature #22212] Add Thread::Backtrace::Location#source_range (eregon) * Proposes a portable API returning a `Ruby::SourceRange` for an exception's `backtrace_locations` or for `caller_locations`. * This gives tools stable start/end line/column coordinates without version-specific `node_id` values ([examples of `node_id` instability](https://bugs.ruby-lang.org/issues/21795#note-32)). * Examples which could use this API instead of currently the CRuby-specific `RubyVM::AST.node_id_for_backtrace_location`, and therefore work reliably on TruffleRuby/JRuby: `Prism.find(Thread::Backtrace::Location)`, [`Rails` exception printing](https://github.com/rails/rails/blob/edf8f12a9f54a476986443070f3b07f300d0955b...), `error_highlight`, `power_assert`. * It does not require the Prism gem or create `Prism::Node` objects, separating source-code location from parsing that code into an AST. * The [implementation](https://github.com/ruby/ruby/pull/18043) reparses on demand to avoid persistent memory overhead, uses source-hash validation based on @mame 's work, and supports `RubyVM.keep_script_lines = true` to avoid re-reading files from disk. * Extensive specs ensure Prism and parse.y return identical user-facing coordinates, including for blocks. * I am looking for matz's approval for the new method. ---------------------------------------- Misc #22221: DevMeeting-2026-08-06 https://bugs.ruby-lang.org/issues/22221#change-118302 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/08/06 13:00-17:00** (JST) Log: *TBD* - Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker. - Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly. - Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue). - We will write a record of the discussion in the file or to each ticket in English. - All activities are best-effort (keep in mind that most of us are volunteer developers). - The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time. - *DO NOT* discuss then on this ticket, please. # Call for agenda items If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format: ``` * [Ticket ref] Ticket title (your name) * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.) ``` Example: ``` * [Feature #14609] `Kernel#p` without args shows the receiver (ko1) * I feel this feature is very useful and some people say :+1: so let discuss this feature. ``` - It is recommended to add a comment by 2026/08/03. We hold a preparatory meeting to create an agenda a few days before the dev-meeting. - The format is strict. We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We may ignore a comment that does not follow the format. - Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion. -- https://bugs.ruby-lang.org/