[experiment] expand: Make #[derive(A, B, ...)] cfg-eval its input only for A, B, ...
#86057
Conversation
|
(rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
rustbot
added
the
S-waiting-on-perf
petrochenkov
removed
the
S-waiting-on-review
|
⌛ Trying commit e45d869 with merge f980a6509ca6ba43d60fdc29723f7b3c7b8497f1... |
|
☀️ Try build successful - checks-actions |
|
Queued f980a6509ca6ba43d60fdc29723f7b3c7b8497f1 with parent 3740ba2, future comparison URL. |
|
Finished benchmarking try commit (f980a6509ca6ba43d60fdc29723f7b3c7b8497f1): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
rustbot
added
S-waiting-on-review
|
Not a regression. |
expand: Move some more derive logic to rustc_builtin_macros And cleanup some `unwrap`s in `cfg_eval`. Refactorings extracted from rust-lang#83354 and rust-lang#86057. r? `@Aaron1011`
expand: Move some more derive logic to rustc_builtin_macros And cleanup some `unwrap`s in `cfg_eval`. Refactorings extracted from rust-lang#83354 and rust-lang#86057. r? ``@Aaron1011``
The second item from #83824 (comment).