Introducing TokenStreams and TokenSlices for procedural macros #34575
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
src/libsyntax/lib.rs
Outdated
There was a problem hiding this comment.
why do you need this? What does core::iter give you that std::iter does not?
src/libsyntax/tokenstream.rs
Outdated
There was a problem hiding this comment.
nit: comments should end with punctuation
src/libsyntax/tokenstream.rs
Outdated
There was a problem hiding this comment.
could use && rather than if ... else { false }
src/libsyntax/tokenstream.rs
Outdated
|
OK, two very minor comments to address, then could you squash the commits please? r+ with that. |
|
☔ The latest upstream changes (presumably #34652) made this pull request unmergeable. Please resolve the merge conflicts. |
cgswords
force-pushed
the
tstream
branch
2 times, most recently
from
f10f932 to
ec6a3d9
Compare
|
Took care of bors concern, too. |
…g unit tests and associated operations.
|
@bors: r+ |
|
📌 Commit 7547596 has been approved by |
Introducing TokenStreams and TokenSlices for procedural macros This pull request introduces TokenStreams and TokenSlices into the compiler in preparation for usage as part of RFC 1566 (procedural macros). r? @nrc
4 participants
This pull request introduces TokenStreams and TokenSlices into the compiler in preparation for usage as part of RFC 1566 (procedural macros).
r? @nrc