-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
clarify that realloc refreshes pointer provenance even when the allocation remains in-place #104568
Conversation
…ation remains in-place
r? @scottmcm (rustbot has picked a reviewer for you, use r? to override) |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
I was about to object that this wouldn't make sense for @bors r+ rollup |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#104537 (fix std::thread docs are unclear regarding stack sizes) - rust-lang#104558 (Don't assume `FILE_ID_BOTH_DIR_INFO` will be aligned) - rust-lang#104564 (interpret: use Either over Result when it is not representing an error condition) - rust-lang#104568 (clarify that realloc refreshes pointer provenance even when the allocation remains in-place) - rust-lang#104611 (rustdoc: use real buttons for scrape examples controls) - rust-lang#104640 (Migrate kdb style to CSS variables) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This matches what C does:
Cc @rust-lang/wg-allocators