-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition future compat lints to {ERROR, DENY} - Take 2 #65785
Conversation
4b41197
to
a512b6c
Compare
a512b6c
to
adfa047
Compare
This comment has been minimized.
This comment has been minimized.
adfa047
to
af3b20a
Compare
This comment has been minimized.
This comment has been minimized.
af3b20a
to
f193001
Compare
The PR builder is finally happy. 🎉 |
Also, |
f193001
to
165f3f1
Compare
@petrochenkov @varkor This should be ready again for review now. |
This comment has been minimized.
This comment has been minimized.
165f3f1
to
2b4565c
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
3f90669
to
f1c5b42
Compare
This comment has been minimized.
This comment has been minimized.
I'm all for this, but the precedent also had fix-PRs open for the crates that will break and did a reverse dependency analysis. I know that doing so is a lot of work, but we do have our stability story. Picking an arbitrary threshold (like 5) of broken crates where it's ok to go to an error, seems a bit odd to me. Then again, we have to do this PR at some point and the forward compat lints have been triggering for a while. I'm unsure how to proceed, thus my question about talking this through in a team meeting or just giving everyone a chance to sign off or comment. |
Seems like all the crates affected are abandoned (which would explain why they haven't been fixed). @bors r+ |
📌 Commit 574d2b8 has been approved by |
Transition future compat lints to {ERROR, DENY} - Take 2 Follow up to rust-lang#63247 implementing rust-lang#63247 (comment). - `legacy_ctor_visibility` (ERROR) -- closes rust-lang#39207 - `legacy_directory_ownership` (ERROR) -- closes rust-lang#37872 - `safe_extern_static` (ERROR) -- closes rust-lang#36247 - `parenthesized_params_in_types_and_modules` (ERROR) -- closes rust-lang#42238 - `duplicate_macro_exports` (ERROR) - `nested_impl_trait` (ERROR) -- closes rust-lang#59014 - `ill_formed_attribute_input` (DENY) -- transitions rust-lang#57571 - `patterns_in_fns_without_body` (DENY) -- transitions rust-lang#35203 r? @varkor cc @petrochenkov
⌛ Testing commit 574d2b8 with merge 230ebbbe9d0ea2faf5fe586b8f3f049b6f571c4b... |
Transition future compat lints to {ERROR, DENY} - Take 2 Follow up to rust-lang#63247 implementing rust-lang#63247 (comment). - `legacy_ctor_visibility` (ERROR) -- closes rust-lang#39207 - `legacy_directory_ownership` (ERROR) -- closes rust-lang#37872 - `safe_extern_static` (ERROR) -- closes rust-lang#36247 - `parenthesized_params_in_types_and_modules` (ERROR) -- closes rust-lang#42238 - `duplicate_macro_exports` (ERROR) - `nested_impl_trait` (ERROR) -- closes rust-lang#59014 - `ill_formed_attribute_input` (DENY) -- transitions rust-lang#57571 - `patterns_in_fns_without_body` (DENY) -- transitions rust-lang#35203 r? @varkor cc @petrochenkov
@bors retry rolled up. |
Rollup of 5 pull requests Successful merges: - #65785 (Transition future compat lints to {ERROR, DENY} - Take 2) - #66007 (Remove "here" from "expected one of X here") - #66043 (rename Memory::get methods to get_raw to indicate their unchecked nature) - #66154 (miri: Rename to_{u,i}size to to_machine_{u,i}size) - #66188 (`MethodSig` -> `FnSig` & Use it in `ItemKind::Fn`) Failed merges: r? @ghost
⌛ Testing commit 574d2b8 with merge 1465351c3dbabfa79ff87afa4e90c34d77be68ae... |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
resolve: Minor cleanup of duplicate macro reexports Enabled by rust-lang#65785 which changed `duplicate_macro_exports` from a lint to a hard error.
resolve: Minor cleanup of duplicate macro reexports Enabled by rust-lang#65785 which changed `duplicate_macro_exports` from a lint to a hard error.
It was not initially clear to me why, after changing `.filter(...).next()` to `.find(...)`, the borrow checker as of Rust 1.41.1 required me to inline `all.lines()` at this point : error[E0596]: cannot borrow `lines` as mutable, as it is not declared as mutable --> tyrga-bin/../build.rs:53:33 | 52 | let lines = all.lines(); | ----- help: consider changing this to be mutable: `mut lines` 53 | let wrote = lines | ^^^^^ cannot borrow as mutable error: aborting due to previous error For more information about this error, try `rustc --explain E0596`. but it [appears][0] that the new error is [expected][1], and that if I had been using `.find()` previously instead of `.filter(...).next()`, I would have seen a non-fatal "compat" lint under previous compiler versions, leading me in the same direction. [0]: rust-lang/rust#68729 [1]: rust-lang/rust#65785
The panics are removed as rust-lang/rust#65785 has made them an error and the compiler will complain anyway for ill formed attributes. The use _could_ allow them, technically. But this doesn't really exist: https://github.com/search?q=allow%28ill_formed_attribute_input%29&type=code Shows 4 occurences at time of commit. I would also think that users that enable this, should know what they are doing ;) Signed-off-by: Marcel Müller <[email protected]>
Follow up to #63247 implementing #63247 (comment).
legacy_ctor_visibility
(ERROR) -- closes Tracking issue forlegacy_constructor_visibility
compatibility lint #39207legacy_directory_ownership
(ERROR) -- closeslegacy_directory_ownership
future-compatibility warnings #37872safe_extern_static
(ERROR) -- closes Tracking issue forsafe_extern_statics
compatibility lint #36247parenthesized_params_in_types_and_modules
(ERROR) -- closesparenthesized_params_in_types_and_modules
future-compatibility warnings #42238duplicate_macro_exports
(ERROR)nested_impl_trait
(ERROR) -- closes Tracking issue fornested_impl_trait
compatibility lint #59014ill_formed_attribute_input
(DENY) -- transitions Tracking issue for future-incompatibility lintill_formed_attribute_input
#57571patterns_in_fns_without_body
(DENY) -- transitions Tracking issue for future-incompatibility lintpatterns_in_fns_without_body
#35203r? @varkor
cc @petrochenkov