Skip to content

Conversation

steveklabnik
Copy link
Contributor

This incorrectly implied that doing things is fine in unsafe code

Fixes #26346

@rust-highfive
Copy link
Contributor

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@@ -33,9 +33,21 @@ in the sections marked `unsafe`.

# What does ‘safe’ mean?

Safe, in the context of Rust, means “doesn’t do anything unsafe.” Easy!
Safe, in the context of Rust, means ‘doesn’t do anything unsafe’. It’s also
important to notice all kinds of behaviors that are certainly bad, but are
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/all kinds/there are kinds/ ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated, let me know what you think :)

This incorrectly implied that doing things is fine in unsafe code

Fixes rust-lang#26346
@Gankra
Copy link
Contributor

Gankra commented Jul 7, 2015

@bors r+

Thanks!

@bors
Copy link
Collaborator

bors commented Jul 7, 2015

📌 Commit bc28e64 has been approved by Gankro

@steveklabnik
Copy link
Contributor Author

@bors: rollup

steveklabnik added a commit to steveklabnik/rust that referenced this pull request Jul 7, 2015
This incorrectly implied that doing things is fine in unsafe code

Fixes rust-lang#26346
bors added a commit that referenced this pull request Jul 7, 2015
@bors bors merged commit bc28e64 into rust-lang:master Jul 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants