With this implemented and then removed after Ruby 4.0.0, Preview 2, is this still planned for completion? Would really like to have this but unclear on the current plan. I assume we will have to wait until Ruby 4.1.0 at best?bkuhlmann (Brooke Kuhlmann)
**Jean**: Sorry, I didn't provide enough context to my original statement. Each year -- about ~2 months before Christmas when a new Ruby version drops -- I release a *patch* version of all my gems that accepts the current version and ...bkuhlmann (Brooke Kuhlmann)
I would also like to know if the next Ruby version is 3.5.0 or 4.0.0 precisely because Ruby doesn't follow Semantic Versioning. Having this knowledge sooner rather than later means I can pin my gemspecs to the correct version (and/or ver...bkuhlmann (Brooke Kuhlmann)
ℹ️ In case it's of interest/inspiration, I released [Inspectable](https://alchemists.io/projects/inspectable) 0.2.0 which tackles what is described in this issue by making it easy to redact sensitive information, slim down verbosity, or ...bkuhlmann (Brooke Kuhlmann)
From an developer ergonomic standoint, could only symbols be used to simplify the syntax further? Example: ``` ruby # First suggestion. def inspect = super(:host, :user)
**Yusuke**: I went hunting for the `Prism.node_for` method/documentation but couldn't find it. If I understand you correctly, I think you are proposing adding the `.node_for` implementation to Prism? If so, I like the detailed informatio...bkuhlmann (Brooke Kuhlmann)
Yeah, eager to see what the consensus on this becomes from the next dev meeting. I like the idea of a `Ruby::SourceLocation` or even a `Ruby::Source` object? The latter would be nice because you could message the instance as `source.cod...bkuhlmann (Brooke Kuhlmann)
**Kevin**: Thanks and thanks for reminding of `RubyVM::InstructionSequence.of().script_lines`. I'm using that as a fallback when the absolute path of the instruction sequence can't be found. **Benoit**: Thanks. I've also updated [Feat...bkuhlmann (Brooke Kuhlmann)