Support useing externally defined macros behind #![feature(use_extern_macros)]#37732
Merged
bors merged 8 commits intorust-lang:masterfrom Nov 17, 2016
Merged
Support useing externally defined macros behind #![feature(use_extern_macros)]#37732bors merged 8 commits intorust-lang:masterfrom
useing externally defined macros behind #![feature(use_extern_macros)]#37732bors merged 8 commits intorust-lang:masterfrom
Conversation
jseyfried
force-pushed
the
use_extern_macros
branch
from
65da379 to
a75cc5b
Compare
Contributor
Author
jseyfried
force-pushed
the
use_extern_macros
branch
4 times, most recently
from
8e1dcf6 to
cc550af
Compare
nrc
approved these changes
Nov 15, 2016
Member
nrc
left a comment
nrc
left a comment
There was a problem hiding this comment.
r = me with the style nits addressed
Member
There was a problem hiding this comment.
formatting nit: prefer one arg per line
Collaborator
|
☔ The latest upstream changes (presumably #37545) made this pull request unmergeable. Please resolve the merge conflicts. |
jseyfried
force-pushed
the
use_extern_macros
branch
from
cc550af to
6cb33a0
Compare
Contributor
Author
|
@bors r=nrc |
Collaborator
|
📌 Commit 6cb33a0 has been approved by |
Collaborator
bors
added a commit
that referenced
this pull request
Nov 17, 2016
Support `use`ing externally defined macros behind `#![feature(use_extern_macros)]` With `#![feature(use_extern_macros)]`, - A name collision between macros from different upstream crates is much less of an issue since we can `use` the macros in different submodules or rename with `as`. - We can reexport macros with `pub use`, so `#![feature(macro_reexport)]` is no longer needed. - These reexports are allowed in any module, so crates can expose a macro-modular interface. If a macro invocation can resolve to both a `use` import and a `macro_rules!` or `#[macro_use]`, it is an ambiguity error. r? @nrc
Collaborator
This was referenced Nov 17, 2016
Merged
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
3 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.
With
#![feature(use_extern_macros)],usethe macros in different submodules or rename withas.pub use, so#![feature(macro_reexport)]is no longer needed.If a macro invocation can resolve to both a
useimport and amacro_rules!or#[macro_use], it is currently an ambiguity error.r? @nrc