bors 8422e27b27 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		2024-10-06 17:00:02 +00:00
..
src	Auto merge of #129670 - est31:cfg_attr_crate_type_name_error, r=Urgau	2024-10-06 17:00:02 +00:00
Cargo.toml	non_local_defs: point to Self and Trait to give more context	2024-05-27 23:59:18 +02:00
messages.ftl	Auto merge of #129670 - est31:cfg_attr_crate_type_name_error, r=Urgau	2024-10-06 17:00:02 +00:00