#1 - feat: add support for (unstable) declarative macros v2 and proc-macros#20
Open
brvtalcake wants to merge 2 commits into
Open
#1 - feat: add support for (unstable) declarative macros v2 and proc-macros#20brvtalcake wants to merge 2 commits into
macros v2 and proc-macros#20brvtalcake wants to merge 2 commits into
Conversation
| @@ -0,0 +1,201 @@ | |||
| use std::{ | |||
There was a problem hiding this comment.
I'm not willing to put build scripts in core. I'd like to avoid them as much as possible in both crates (although I suspect cfg is gonna have to have some), but especially in core, since doing so really hurts build times which discourages use of this crate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request is the first to examine and to merge. It contains additions and modifications needed to support the actual parsing and processing of macros v2 and proc-macros. Please consider the fact that it may not pass ci runs since a lot of code will remain unused (i.e.
dead_code) while the other PRs are not also merged