Merged
Contributor
LGTM. @rust-lang/compiler, looks like this should've been removed before 1.0 - can we do that now?
Collaborator
☔ The latest upstream changes (presumably #36601) made this pull request unmergeable. Please resolve the merge conflicts.
Member
ping r? @eddyb, perhaps this should be nominated for a compiler team discussion?
nikomatsakis
added
T-compiler
and removed T-lang
Relevant to the language teamlabels
Nov 3, 2016Contributor
This is really a @rust-lang/compiler team problem.
Wearing my compiler hat, I propose that we do a quick crater run to see if anyone is affected and remove it. Basically the normal bug fix protocol. At worst, we can have a warning period, but this seems like one of those cases where it's probably not needed.
Contributor
We can actually skip crater and just (rip)grep the sources of crates.io I guess, even easier.
label
Nov 9, 2016Contributor
This looks like it removes all tests around #[macro_escape]. Can it instead add a test that captures what does happen when you mention macro_escape? Is it an error?
Contributor Author
@brson Currently, #[macro_escape] would have no effect, but I think it should be a custom_attribute feature error like other unknown attributes (I'll update and add a test when we want to land).
At worst, we can have a warning period
It has been a deprecation warning since the beginning of 2015.
At least one of the grepped crates (immutable) is a real regression (many are already broken or have a dead GH repository link). There's very little downside to keeping #[macro_escape], so I'm going to close this PR until there are no regressing crates.