-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
macros: Future proof #[no_link]
#37247
Merged
Merged
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
jseyfried
force-pushed
the
future_proof_no_link
branch
from
October 18, 2016 07:32
affcf88
to
bb0b961
Compare
☔ The latest upstream changes (presumably #37269) made this pull request unmergeable. Please resolve the merge conflicts. |
jseyfried
force-pushed
the
future_proof_no_link
branch
from
October 19, 2016 10:05
bb0b961
to
b283aaf
Compare
@nikomatsakis or @eddyb can we get a crater run for this PR please? r=me with a clean crater run |
@bors r=nrc |
📌 Commit b283aaf has been approved by |
bors
added a commit
that referenced
this pull request
Oct 21, 2016
macros: Future proof `#[no_link]` This PR future proofs `#[no_link]` for macro modularization (cc #35896). First, we resolve all `#[no_link] extern crate`s. `#[no_link]` crates without `#[macro_use]` or `#[macro_reexport]` are not resolved today, this is a [breaking-change]. For example, ```rust ``` Any breakage can be fixed by simply removing the `#[no_link] extern crate`. Second, `#[no_link] extern crate`s will define an empty module in type namespace to eventually allow importing the crate's macros with `use`. This is a [breaking-change], for example: ```rust mod syntax {} //< This becomes a duplicate error. ``` r? @nrc
brson
added
the
relnotes
Marks issues that should be documented in the release notes of the next release.
label
Oct 24, 2016
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.
This PR future proofs
#[no_link]
for macro modularization (cc #35896).First, we resolve all
#[no_link] extern crate
s.#[no_link]
crates without#[macro_use]
or#[macro_reexport]
are not resolved today, this is a [breaking-change]. For example,Any breakage can be fixed by simply removing the
#[no_link] extern crate
.Second,
#[no_link] extern crate
s will define an empty module in type namespace to eventually allow importing the crate's macros withuse
. This is a [breaking-change], for example:r? @nrc