<masak> TimToady_: ooc, do you agree that tracing a grammar breaks LTM matching? https://github.com/jnthn/grammar-debugger/issues/13#issuecomment-229940842 <jnthn> The solution, for whoever fancies implementing it, is probably to mix a role into the tracing closure that we hand back. <jnthn> Where said role has the methods like !NFA or whatever on it and forwards them to the underlying code-ref <jnthn> (That of the original rule) <jnthn> Since the reason for the problem is, afaict, that the closure we return instead of the method lacks the NFA <jnthn> OTOH, we could switch the NFA resolution to use lookup instead of find_method since it's after the original declarator <jnthn> Then Grammar::Tracer will just work and everyone won't have to re-solve the same problem if doing similar things. <jnthn> In fact that's probably the better way, and then Grammar::Tracer will Just Work again. <jnthn> So let's do it that way :) <jnthn> Then it'll freely fix other modules like Grammar::Debugger and Grammar::Profiler too I suspect. * masak adds this insight to the RT ticket <masak> jnthn: um, where would the solution reside? in Rakudo, or in Grammar::Tracer? <jnthn> masak: NQP