Description
Stability checking for macro_rules!
was fixed in #48524, but uses of declarative macros 2.0 (macro
items) are still not checked for stability.
ORIGINAL ISSUE:
Why does this compile?
fn main() {
__thread_local_inner!(i32, 42);
}
__thread_local_inner
is marked #[unstable(...)] #[allow_internal_unstable]
.
Activity
petrochenkov commentedon Jun 4, 2016
Because macros are not checked for stability!
At least this was the case when I made stability annotations on public macros mandatory in hopes of a better future.
jseyfried commentedon Jun 10, 2016
cc me
abonander commentedon Feb 25, 2018
I'm looking into implementing this, however are we just looking at
macro_rules!
macros for now or proc-macro and syntax extension invocations as well?cc @nrc
Auto merge of #48524 - abonander:check-macro-stability, r=<try>
petrochenkov commentedon Mar 16, 2018
@abonander
I'm reopening this because macros 2.0 (
macro
items) are not checked for stability yet.10 remaining items