-
Notifications
You must be signed in to change notification settings - Fork 152
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
Keep as much span info as possible #252
Conversation
@TeXitoi Pretty much ready, waiting on review |
ping @TeXitoi , sorry for being annoying but I need your opinion to move on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I lightly reviewed and it seems fine to me.
for #156 a separate commit would be great. |
Well, that's final line. I'll go work on AST implementation, should be done in a week or so (I'm kind of overloaded by work/life stuff right now, sorry) |
ping @TeXitoi |
cc @TeXitoi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changelog entry and I merge.
Sorry to be long to review.
There is an error message change that fail the nightly build :-( |
@TeXitoi They look identical. I'll investigate in few hours |
There is an extra message after the ^^^^^^^^ |
Fucking nightly! Will fix |
Most of `quote!` invocations are replaced with `quote_spanned!` ones. Now everywhere - sometimes it's pointless, sometimes we don't have any meaningless location to toke a span from, sometimes I just can't workaround the current implementation - too much changes.
Thanks. |
Closes #247
Work-in-progress, just so you could state your opinion on this changes
Em, fix to #156 is also here, I can extract it to a separate PR if you want