We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
0.6.20
I found myself always need to surround my parser in trace function, so why don't we add a "trace" macro to make us more lazy?
trace
Something like:
#[trace] fn my_parser(input: I) -> PResult<O> { ... }
will be expanded to:
fn my_parser(input: I) -> PResult<O> { trace("my_parser", move |input: &mut _| { ... }).parse_next(input) }
No response
The text was updated successfully, but these errors were encountered:
I'm trying to hold off on having proc macros. There is an RFC for attribute macro-by-example. That would allow us to support a #[winnow::trace] macro.
#[winnow::trace]
Sorry, something went wrong.
No branches or pull requests
Please complete the following tasks
winnow version
0.6.20
Describe your use case
I found myself always need to surround my parser in
trace
function, so why don't we add a "trace" macro to make us more lazy?Describe the solution you'd like
Something like:
will be expanded to:
Alternatives, if applicable
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: