Get rustc version string at rustversion crate build time #11
Conversation
This file contains 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
Summary:There's no need to fetch the rustc version at proc-macro invocation time because its always constant for a given compilation of the crate. Since Rust doesn't have a stable ABI, the compiler used to compile rustversion is guaranteed to be the same as the one invoking the rustversion proc macro.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary:There's no need to fetch the rustc version at proc-macro
invocation time because its always constant for a given compilation of
the crate. Since Rust doesn't have a stable ABI, the compiler used to
compile rustversion is guaranteed to be the same as the one invoking the
rustversion proc macro.