Akim Demaille

steep does choke on endless defs.

I have a similar failure, but with a different pattern (heavily stripped down) ```ruby case [self, other] in [MetaType[id], *] if other in MetaType[id2] end end ``` ``` /opt/local/lib/ruby3.1/gems/3.1.0/gems/yard-0.9.27/lib/yard/parser/ruby/ast_node.rb:274:in `first':...

I believe the proper fix is in `lib/yard/parser/ruby/ast_node.rb` to replace: ```ruby def line line_range && line_range.first end ``` by ```ruby def line line_range && line_range.begin end ``` since `begin` always...

It turns out I also need to change `reset_line_info` in the same file: ```ruby self.line_range = Range.new(f.line_range.begin || 1, l.line_range.last) self.source_range = Range.new(f.source_range.begin || 1, l.source_range.last) ``` instead of using...

Markus, In trying to find something to reproduce our failure, I may well have written something actually more complex than our original use case. And so far, we can't reproduce...

Hey Markus, Oh, you have a new face :) Unparser is the final part of a parse|transform|unparse pipe. We don't care about exact syntactic round tripping, we just care about...

Markus, I have been told that since we have something that works (and works around that particular issue), we won't change it again. So I guess we'll stick to Parser's...

Markus, Yes, I know, that was very clear. Yet this stuff is in production, and the guy in charge of that does not want to change it now. Maybe in...

Hi Markus, No, we are still using the "native" AST from parser itself.

I perfectly understand all these points, but the decision is not mine.  I'm just a proxy here.