-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 8 pull requests #106616
Rollup of 8 pull requests #106616
Conversation
Co-authored-by: Esteban Kuber <[email protected]>
… the correct allocator.
…lnay Don't derive Debug for `OnceWith` & `RepeatWith` Closures don't impl Debug, so the derived impl is kinda useless. The behavior of not debug-printing closures is consistent with the rest of the iterator adapters/sources.
Mention "signature" rather than "fn pointer" when impl/trait methods are incompatible Fixes rust-lang#80929 Fixes rust-lang#67296
…r=Nilstrieb Structured suggestion for `&mut dyn Iterator` when possible Fix rust-lang#37914.
…clone, r=estebank Suggest using clone when we have &T and T implemented Clone Fixes rust-lang#106443
Document that `Vec::from_raw_parts[_in]` must be given a pointer from the correct allocator. Currently, the documentation of `Vec::from_raw_parts` and `Vec::from_raw_parts_in` says nothing about what allocator the pointer must come from. This PR adds that missing information explicitly.
…y-err, r=estebank Suppress type errors that come from private fields Fixes rust-lang#57320 There was some discussion here (rust-lang#57320 (comment)), but I honestly think the second error is worth suppressing regardless. I would be open to feedback though -- perhaps we can suppress the `.len()` suggestion if there's type error (since we have access to [`Expectation`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir_typeck/enum.Expectation.html), we can determine that). r? ``@estebank``
…r=Mark-Simulacrum Add goml scripts to tidy checks r? ``@notriddle``
…ompiler-errors Do not emit structured suggestion for turbofish with wrong span Fix rust-lang#79161.
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: a377893da2 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (2e677c0): 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.
|
Successful merges:
OnceWith
&RepeatWith
#104163 (Don't derive Debug forOnceWith
&RepeatWith
)&mut dyn Iterator
when possible #106363 (Structured suggestion for&mut dyn Iterator
when possible)Vec::from_raw_parts[_in]
must be given a pointer from the correct allocator. #106584 (Document thatVec::from_raw_parts[_in]
must be given a pointer from the correct allocator.)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup