libcore tests: avoid int2ptr casts#98587
Conversation
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
r? @thomcc (rust-highfive has picked a reviewer for you, use r? to override) |
|
lgtm @bors r+ |
|
📌 Commit 8c977cf has been approved by |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
@bors rollup=always |
|
It's not always ideal to rollup tests I think, since sometimes they fail in rollup. But it also doesn't really matter. |
|
Yeah but this seems like a change where I trust PR CI. And we need rollups right now.^^ |
…askrgr Rollup of 9 pull requests Successful merges: - rust-lang#98331 (Fix rustdoc argument error) - rust-lang#98506 (Fix span issues in object safety suggestions) - rust-lang#98563 (interpret: refactor allocation info query) - rust-lang#98576 (small regions refactoring) - rust-lang#98577 (Fix "kind" for associated types in trait implementations in rustdoc JSON) - rust-lang#98578 (Remove eddyb from miri failure pings) - rust-lang#98579 (liballoc tests: avoid int2ptr cast) - rust-lang#98581 (Add triagebot mentions.) - rust-lang#98587 (libcore tests: avoid int2ptr casts) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
We don't need any of these pointers to actually be dereferenceable so using
ptr::invalidshould be fine. And then we can run Miri with strict provenance enforcement on the tests.