-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support tracing across reference boundaries #86
Comments
Ah, I see now why this is a little tricky. Hmmm |
Reference boundaries disappear when the parser is built, I don't see how they would affect the trace if it is applied just before parsing? Can you provide an example? |
So right now I'm applying the trace inside my |
Yes. That worked perfectly. Thank you. |
Yeah, it does not work inside the |
Hi there,
I noticed that
trace
parsers are unable to trace the "children" ofReference
parsers, which would be handy.I got around this without too much trouble (little code change, and introduced the trace in the referenced function), but it would be really nice to see a cohesive trace through the entirety of the input, with proper indentation and all that.
Anyway, thanks! This library has proven useful for a tiny DSL I'm writing.
The text was updated successfully, but these errors were encountered: