TRPL: unsafe -> raw pointers #24631
Merged
TRPL: unsafe -> raw pointers #24631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(rust_highfive has picked a reviewer for you, use r? to override) |
| println!("raw points at {}", points_at); | ||
| ``` | ||
|
|
||
| For more operations on raw pointers, see [ther API documentation][rawapi]. |
steveklabnik
force-pushed
the
unsafe_guide
branch
from
1b4f25c to
1150fb0
Compare
Many unsafe features are now in the unstable section, so this section is really just about raw pointers now. That also makes sense for its place in the TOC. This addresses part of rust-lang#12905.
| ``` | ||
|
|
||
| ## Raw pointers | ||
| % Raw Pointers |
There was a problem hiding this comment.
Was this file intended for deletion?
There was a problem hiding this comment.
Yes, it effectively got moved to the other one. I'm working on a new, general 'unsafe' guide now, was just gonna send a different PR.
|
r=me if unsafe-code.md should be deleted, and also r=me if it shouldn't :) |
|
@bors: r=alexcrichton rollup |
|
📌 Commit 1150fb0 has been approved by |
| % Raw Pointers | ||
|
|
||
| Rust has a number of different smart pointer types in its standard library, but | ||
| there are two types that are extra-special. Much of Rust’s safety comes from |
There was a problem hiding this comment.
Which two? & and &mut? or *const and *mut? It's seems to me that the raw pointer types are the least special (at least when compared to C/C++/other languages).
Also, I wouldn't call the raw pointer types "smart pointers".
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this pull request
Apr 21, 2015
…ichton Many unsafe features are now in the unstable section, so this section is really just about raw pointers now. That also makes sense for its place in the TOC. This addresses part of rust-lang#12905.
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this pull request
Apr 21, 2015
rust-lang#24631 is related, as it will delete this from the TOC, but I want to keep it here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many unsafe features are now in the unstable section, so this section is
really just about raw pointers now. That also makes sense for its place
in the TOC.
This addresses part of #12905.