-
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 7 pull requests #91933
Rollup of 7 pull requests #91933
Conversation
`[].split_inclusive()` currently yields a single, empty slice. That's different from `"".split_inslusive()`, which yields no output at all. I think that makes the slice version harder to use. The case where I ran into this bug was when writing code for generating a diff between two slices of bytes. I wanted to prefix removed lines with "-" and a added lines with "+". Due to `split_inclusive()`'s current behavior, that means that my code prints just a "-" or "+" for empty files. I suspect most existing callers have similar "bugs" (which would be fixed by this patch). Closes rust-lang#89716.
Co-authored-by: Esteban Kuber <[email protected]>
Previously some code paths would fail to evaluate the rvalue, while incorrectly indicating success with `Ok`. As a result the previous value of lhs could have been incorrectly const propagated.
…=m-ou-se Make split_inclusive() on an empty slice yield an empty output `[].split_inclusive()` currently yields a single, empty slice. That's different from `"".split_inslusive()`, which yields no output at all. I think that makes the slice version harder to use. The case where I ran into this bug was when writing code for generating a diff between two slices of bytes. I wanted to prefix removed lines with "-" and a added lines with "+". Due to `split_inclusive()`'s current behavior, that means that my code prints just a "-" or "+" for empty files. I suspect most existing callers have similar "bugs" (which would be fixed by this patch). Closes rust-lang#89716.
… r=jackh726 regression test for issue 87490 Closes rust-lang#87490
…i-obk Recover on invalid operators `<>` and `<=>` Thanks to rust-lang#89871 for showing me how to do this. Next, I think it'd be nice to recover on `<=>` too, like rust-lang#89871 intended, if this even works.
Fix typo for MutVisitor Fix typo for MutVisitor.
Return an error when `eval_rvalue_with_identities` fails Previously some code paths would fail to evaluate the rvalue, while incorrectly indicating success with `Ok`. As a result the previous value of lhs could have been incorrectly const propagated. Fixes rust-lang#91725. r? `@oli-obk`
…ister Avoid suggest adding `self` in visibility spec Fixes rust-lang#91783
Looser check for overflowing_binary_op Fix for issue rust-lang#91636 tight check resulted in ICE, this makes the check a little looser. It seems `eq` allows comparing of `supertype` and `subtype` if `lhs = supertype` and `rhs = subtype` but not vice versa, is this intended behavior ?
@bors r+ rollup=never p=7 |
📌 Commit bae9270 has been approved by |
⌛ Testing commit bae9270 with merge 3464916c81a5775d48944f00bd9a9571cf4bc3bd... |
💔 Test failed - checks-actions |
🙄
@bors retry spurious download failure |
@bors p=16 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (d594910): 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:
<>
and<=>
#91597 (Recover on invalid operators<>
and<=>
)eval_rvalue_with_identities
fails #91786 (Return an error wheneval_rvalue_with_identities
fails)self
in visibility spec #91798 (Avoid suggest addingself
in visibility spec)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup