Skip to content

Commit 5db3c5f

Browse files
committed
Auto merge of rust-lang#139814 - matthiaskrgr:rollup-lxkkcz6, r=matthiaskrgr
Rollup of 8 pull requests Successful merges: - rust-lang#139127 (Fix up partial res of segment in primitive resolution hack) - rust-lang#139392 (Detect and provide suggestion for `&raw EXPR`) - rust-lang#139767 (Visit place in `BackwardIncompatibleDropHint` statement) - rust-lang#139777 (Remove `define_debug_via_print` for `ExistentialProjection`, use regular structural debug impl) - rust-lang#139796 (ptr docs: add missing backtics around 'usize') - rust-lang#139801 (Add myself to mailmap) - rust-lang#139804 (use `realpath` in `bootstrap.py` when creating build-dir) - rust-lang#139807 (Improve wording of post-merge report) r? `@ghost` `@rustbot` modify labels: rollup
2 parents 543820f + aa425a8 commit 5db3c5f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Diff for: core/src/ptr/mod.rs

+1-1
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@
278278
//! ### Using Strict Provenance
279279
//!
280280
//! Most code needs no changes to conform to strict provenance, as the only really concerning
281-
//! operation is casts from usize to a pointer. For code which *does* cast a `usize` to a pointer,
281+
//! operation is casts from `usize` to a pointer. For code which *does* cast a `usize` to a pointer,
282282
//! the scope of the change depends on exactly what you're doing.
283283
//!
284284
//! In general, you just need to make sure that if you want to convert a `usize` address to a

0 commit comments

Comments
 (0)