-
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
Rollup of 15 pull requests #89545
Rollup of 15 pull requests #89545
Conversation
Supertraits of specialization markers could circumvent checks for min_specialization. Elaborating predicates prevents this.
The previous macro_rules! parsers failed when an additional modifier was added with ambiguity errors. The error is pretty unclear as to what exactly the cause here is, but this change simplifies the argument parsing code such that the error is avoided.
As the docs at the top of the file say, it is an overloaded pass and actually runs two lints.
Fixed numerus of error message Removed superfluous argument Using pluralize!() instead of code duplication Adjusted a test
…htriplett Stabilize try_reserve Stabilization PR for the [`try_reserve` feature](rust-lang#48043 (comment)).
Perform type inference in range pattern Fix rust-lang#88074
Added abs_diff for integer types. Closes rust-lang#62111.
path.push() should work as expected on windows verbatim paths On Windows, std::fs::canonicalize() returns an so-called UNC path. UNC paths differ with regular paths because: - This type of path can much longer than a non-UNC path (32k vs 260 characters). - The prefix for a UNC path is ``Component::Prefix(Prefix::DiskVerbatim(..)))`` - No `/` is allowed - No `.` is allowed - No `..` is allowed Rust has poor handling of such paths. If you join a UNC path with a path with any of the above, then this will not work. I've implemented a new method `fn join_fold()` which joins paths and also removes any `.` and `..` from it, and replaces `/` with `\` on Windows. Using this function it is possible to use UNC paths without issue. In addition, this function is useful on Linux too; paths can be appended without having to call `canonicalize()` to remove the `.` and `..`. This PR needs test cases, which can I add. I hope this will a start of a discussion.
…komatsakis Correctly handle supertraits for min_specialization Supertraits of specialization markers could circumvent checks for min_specialization. Elaborating predicates prevents this. r? ````@nikomatsakis````
Update to the final LLVM 13.0.0 release
…-obk Fix bug with query modifier parsing The previous macro_rules! parsers failed when an additional modifier was added with ambiguity errors. The error is pretty unclear as to what exactly the cause here is, but this change simplifies the argument parsing code such that the error is avoided. Extracted from other work, and somewhat duplicates 0358edeb5 from rust-lang#85830, but this approach seems a little simpler to me. Not technically currently necessary but seems like a good cleanup.
…lett Fix extra `non_snake_case` warning for shorthand field bindings Fixes rust-lang#89469. The problem is the innermost `if` condition here: https://github.com/rust-lang/rust/blob/d14731cb3ced8318d7fc83cbe838f0e7f2fb3b40/compiler/rustc_lint/src/nonstandard_style.rs#L435-L452 This code runs for every `PatKind::Binding`, so if a struct has multiple fields, say A and B, and both are bound in a pattern using shorthands, the call to `self.check_snake_case()` will indeed be skipped in the `check_pat()` call for `A`; but when `check_pat()` is called for `B`, the loop will still iterate over `A`, and `field.ident (= A) != ident (= B)` will be true. I have fixed this by only looking at non-shorthand bindings, and only the binding that `check_pat()` was actually called for.
rustdoc: Improve doctest pass's name and module's name As the docs at the top of the file say, it is an overloaded pass and actually runs two lints.
Fixed numerus of error message When there are redundant trait requirements and these are hidden, a message is generated by the following code snippet: `format!("{} redundant requirements hidden", count)` But if there is only a single hidden requirement, it will still print this message in plural instead of singular.
…ckh726 Add test for issue 89118. This PR adds a test for issue 89118. Closes rust-lang#89118.
…nkov Try to recover from a `=>` -> `=` or `->` typo in a match arm Fixes rust-lang#89396.
Deny `where` clauses on `auto` traits Fixes rust-lang#84075.
…=lnicola ⬆️ rust-analyzer
update Miri Let's get the recent fixes and improvements shipped. r? ````@ghost````
@bors r+ p=5 |
📌 Commit 2ae8ced has been approved by |
🌲 The tree is currently closed for pull requests below priority 4. This pull request will be tested once the tree is reopened. |
@bors p=5 |
@bors treeclosed- let stuff land overnight |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a804c4b): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Successful merges:
non_snake_case
warning for shorthand field bindings #89473 (Fix extranon_snake_case
warning for shorthand field bindings)=>
->=
or->
typo in a match arm #89487 (Try to recover from a=>
->=
or->
typo in a match arm)where
clauses onauto
traits #89494 (Denywhere
clauses onauto
traits)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup