-
Notifications
You must be signed in to change notification settings - Fork 13.3k
clarify pointer offset function safety concerns #52668
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
I vaguely recall there being a PR for this previously, or at least an issue, but I can't find it. Maybe @rkruppe remembers? |
@bors r+ rollup |
📌 Commit fb08915 has been approved by |
This discrepancy with ptrtoint+arithmetic+inttoptr has been brought up multiple times in the past (often by @RalfJung IIRC 😄) but I don't recall a docs PR off-hand. |
Same here. But I looked through the PRs I authored and could not find any. |
Ah, found something: #45719 |
clarify pointer offset function safety concerns
Rollup of 7 pull requests Successful merges: - #52391 (Add unaligned volatile intrinsics) - #52402 (impl PartialEq+Eq for BuildHasherDefault) - #52645 (Allow declaring existential types inside blocks) - #52656 (Stablize Redox Unix Sockets) - #52658 (Prefer `Option::map`/etc over `match` wherever it improves clarity) - #52668 (clarify pointer offset function safety concerns) - #52677 (Release notes: add some missing 1.28 libs stabilization) Failed merges: r? @ghost
Fixes #45719