-
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 5 pull requests #80212
Rollup of 5 pull requests #80212
Conversation
…=m-ou-se Stabilize `core::slice::fill` Tracking issue rust-lang#70758 Stabilizes the `core::slice::fill` API in Rust 1.50, adding a `memset` doc alias so people coming from C/C++ looking for this operation can find it in the docs. This API hasn't seen any changes since we changed the signature in rust-lang#71165, and it seems like the right time to propose stabilization. Thanks! r? ``@m-ou-se``
or_patterns: implement :pat edition-specific behavior cc rust-lang#54883 ``@joshtriplett`` This PR implements the edition-specific behavior of `:pat` wrt or-patterns, as determined by the crater runs and T-lang consensus in rust-lang#54883 (comment). I believe this can unblock stabilization of or_patterns. r? ``@petrochenkov``
…, r=RalfJung Fix memory leak in test "mem::uninit_write_slice_cloned_no_drop" This fixes rust-lang#80116. I replaced the `Rc` based method I was using with a type that panics when dropped.
…lcnr Make BoundRegion have a kind of BoungRegionKind Split from rust-lang#76814 Also includes making `replace_escaping_bound_vars` only return `T` Going to r? ```@lcnr``` Feel free to reassign
…ring, r=GuillaumeGomez,jyn514 impl Default for LangString, replacing all_false by default Fix rust-lang#80015 ``@rustbot`` label C-cleanup T-rustdoc A-markdown-parsing
The job Click to see the possible cause of the failure (guessed by this bot)
|
☔ The latest upstream changes (presumably #80253) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
Most of these were merged. |
Successful merges:
core::slice::fill
#79213 (Stabilizecore::slice::fill
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup