about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2019-11-04 12:16:00 +0000
committerbors <bors@rust-lang.org>2019-11-04 12:16:00 +0000
commit2477e2493e67527fc282c7239e019f7ebd513a1a (patch)
tree69f87eb309163474b2fd45d98ec4dd1413cc4e9d /src/libstd/sys/unix/stack_overflow.rs
parentab6e47851b51a413db5d721f25d714653e7549fd (diff)
parente7cedc9972ae753402fece658b5b9f580f4fc5f3 (diff)
downloadrust-2477e2493e67527fc282c7239e019f7ebd513a1a.tar.gz
rust-2477e2493e67527fc282c7239e019f7ebd513a1a.zip
Auto merge of #66078 - petrochenkov:gateout, r=Centril
expand: Feature gate out-of-line modules in proc macro input

Extracted from https://github.com/rust-lang/rust/pull/64273.

We are currently gating attributes applied directly to `mod` items because there are unresolved questions about out-of-line modules and their behavior is very likely to change.

However, you can sneak an out-of-line module into an attribute macro input using modules nested into other items like
```rust
#[my_attr]
fn m() {
    #[path = "zzz.rs"]
    mod n; // what tokens does the `my_attr` macro see?
}
```
This PR prevents that and emits a feature gate error for this case as well.

r? @Centril
It would be great to land this before beta.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions