about summary refs log tree commit diff
path: root/src/librustdoc/html/static/js/source-script.js
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2022-01-17 02:06:54 +0000
committerbors <bors@rust-lang.org>2022-01-17 02:06:54 +0000
commitfd20513f52b1e6a7799fd291c1a5979dd65678ac (patch)
tree181a0c4cab7c780672c067e60d0109250f167ef7 /src/librustdoc/html/static/js/source-script.js
parent1fbd6aedb3474d2a5d70839a42c80d869749d8ff (diff)
parente87ce7ad7463eb49becb931d499c3cf5713cb1b9 (diff)
downloadrust-fd20513f52b1e6a7799fd291c1a5979dd65678ac.tar.gz
rust-fd20513f52b1e6a7799fd291c1a5979dd65678ac.zip
Auto merge of #92473 - petrochenkov:ltrattr2, r=Aaron1011
expand: Pick `cfg`s and `cfg_attrs` one by one, like other attributes

This is a rebase of https://github.com/rust-lang/rust/pull/83354, but without any language-changing parts ~(except for https://github.com/rust-lang/rust/pull/84110)~, i.e. the attribute expansion order is the same.

This is a pre-requisite for any other changes making cfg attributes closer to regular macro attributes
- Possibly changing their expansion order (https://github.com/rust-lang/rust/issues/83331)
- Keeping macro backtraces for cfg attributes, or otherwise making them visible after expansion without keeping them in place literally (https://github.com/rust-lang/rust/pull/84110).

Two exceptions to the "one by one" behavior are:
- cfgs eagerly expanded by `derive` and `cfg_eval`, they are still expanded in a batch, that's by design.
- cfgs at the crate root, they are currently expanded not during the main expansion pass, but before that, during `#![feature]` collection. I'll try to disentangle that logic later in a separate PR.

r? `@Aaron1011`
Diffstat (limited to 'src/librustdoc/html/static/js/source-script.js')
0 files changed, 0 insertions, 0 deletions