diff options
| author | bors <bors@rust-lang.org> | 2024-10-06 17:00:02 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-10-06 17:00:02 +0000 |
| commit | 8422e27b276fade36294d3ba13a754cf48459c7a (patch) | |
| tree | f198ab12983956b96dbf4274816291c3ba6f5a75 /compiler/rustc_const_eval/src | |
| parent | 373971abe48287f47ead6304b19279f34b6fcce5 (diff) | |
| parent | 00ed47b8496bacb9da0196127508e07ba5d14bb4 (diff) | |
| download | rust-8422e27b276fade36294d3ba13a754cf48459c7a.tar.gz rust-8422e27b276fade36294d3ba13a754cf48459c7a.zip | |
Auto merge of #129670 - est31:cfg_attr_crate_type_name_error, r=Urgau
Make deprecated_cfg_attr_crate_type_name a hard error Turns the forward compatibility lint added by #83744 into a hard error, so now, while the `#![crate_name]` and `#![crate_type]` attributes are still allowed in raw form, they are now forbidden to be nested inside a `#![cfg_attr()]` attribute. The following will now be an error: ```Rust #![cfg_attr(foo, crate_name = "foobar")] #![cfg_attr(foo, crate_type = "bin")] ``` This code will continue working and is not deprecated: ```Rust #![crate_name = "foobar"] #![crate_type = "lib"] ``` The reasoning for this is explained in #83744: it allows us to not have to cfg-expand in order to determine the crate's type and name. As of filing the PR, exactly two years have passed since #99784 has been merged, which has turned the lint's default warning level into an error, so there has been ample time to move off the now-forbidden syntax. cc #91632 - tracking issue for the lint
Diffstat (limited to 'compiler/rustc_const_eval/src')
0 files changed, 0 insertions, 0 deletions
