-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Clippy subtree sync #117979
Clippy subtree sync #117979
Conversation
Most notably, this commit changes the `pub use crate::*;` in that file to `use crate::*;`. This requires a lot of `use` items in other crates to be adjusted, because everything defined within `rustc_span::*` was also available via `rustc_span::source_map::*`, which is bizarre. The commit also removes `SourceMap::span_to_relative_line_string`, which is unused.
…dnet Fix `dbg_macro` semi span calculation `span_including_semi` was using a `BytePos` to index into a file's source which happened to work because the root file of the test started at `BytePos` 0, it didn't work for other files changelog: none
`rustc_span` cleanups Just some things I found while looking over this crate. r? `@oli-obk`
[`unused_enumerate_index`]: don't ICE on empty tuples Fixes rust-lang#11755 changelog: [`unused_enumerate_index`]: don't ICE on empty tuples I'm going to nominate for beta backport because the code that is needed to trigger this seems likely to occur in real code `@rustbot` label +beta-nominated
update references of old `msrvs` and `conf` paths In rust-lang#11685, `clippy_lints::utils::conf` and `clippy_utils::msrvs` were moved to a separate `clippy_config` crate. I noticed that not all references to those paths were updated, so this small PR intends to fix those. changelog: none
Make SpanlessEq more consistent 1) Remove wildcard as requested in rust-lang/rust-clippy#10267. 2) Implement `hir_utils::eq_expr` for `ExprKind::Closure`, `ExprKind::ConstBlock`, `ExprKind::InlineAsm` and `ExprKind::Yield`. 3) Reorder branches of `hir_utils::eq_expr` to be in alphabetical order. --- changelog: none
Fixes: rust-lang#11714 changelog: [`arc_with_non_send_sync`]: Suggest RC over unsafe impl Co-authored-by: Alejandra González <blyxyas@gmail.com>
[arc_with_non_send_sync] Improve suggested resolution Fixes: rust-lang#11714 Improved the lint message for [`arc_with_non_send_sync`] to suggest using `RC` unless user needs an Arc, then suggests wrapping in a mutex, and then suggests implementing `Sync` and `Send`. --- changelog: [`arc_with_non_send_sync`]: Suggest RC over unsafe impl of Send and Sync
fixes: rust-lang#11775 current state: indiscriminately emits the lint for mod files in tests. The following tests/ common/ mod.rs test.rs is a common pattern for code shared across the tests and is suggested in the rust book. The change adds an additional check to verify that the mod file is not in tests. changelog: Fix [`mod_module_files`]: false positive for mod files in tests folder
[`mod_module_files`] Don't emit lint for mod.rs in tests fixes: rust-lang#11775 current state: indiscriminately emits the lint for mod files in tests. The following ``` tests/ common/ mod.rs test.rs ``` is a common pattern for code shared across the tests and is suggested in the rust book. The change adds an additional check to verify that the mod file is not in tests. changelog: Fix [`mod_module_files`]: false positive for mod files in tests folder
Rustup r? `@ghost` changelog: none
@bors r+ p=1 |
Clippy subtree sync r? `@Manishearth`
💔 Test failed - checks-actions |
@bors retry network problems again |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a577704): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 675.791s -> 676.528s (0.11%) |
r? @Manishearth