diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-09-02 22:35:22 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-02 22:35:22 +0200 |
| commit | 9dad90a22a3489cfb07ba66f615886a910a83095 (patch) | |
| tree | f754d22418ac4b9091bad135aacc5889fc28fe7a /tests/rustdoc-js-std/parser-errors.js | |
| parent | 3ddf061926533a2db9368b2e27536aeca6fbc1fe (diff) | |
| parent | 7494224e74682a7dff39747ef5007ad7df889e2b (diff) | |
| download | rust-9dad90a22a3489cfb07ba66f615886a910a83095.tar.gz rust-9dad90a22a3489cfb07ba66f615886a910a83095.zip | |
Rollup merge of #129892 - oskgo:clarify-slice-from-raw, r=RalfJung
Clarify language around ptrs in slice::raw More specifically we explicitly mention that the pointer should be non-null as a top level requirement. Nullptrs are always valid for zero sized operations, so just validity (and alignment) does not guarantee non-nullness as implied in the existing docs. We also explicitly call out ZSTs as an additional example where perhaps unintuitively alignment and non-nullness still have to hold. Finally we change `data` in the range functions to `start`, which seems like a typo to me. Touches docs for #89792 r? RalfJung
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions