Skip to content

"unsafe" doesn't sound unsafe enough #666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lkuper opened this issue Jul 11, 2011 · 6 comments
Closed

"unsafe" doesn't sound unsafe enough #666

lkuper opened this issue Jul 11, 2011 · 6 comments
Labels
A-Unicode Area: Unicode

Comments

@lkuper
Copy link
Contributor

lkuper commented Jul 11, 2011

The compiler should accept both "unsafe" and "☢" as synonyms, and the pretty-printer should canonicalize to ☢. Implement this.
@ghost ghost assigned pfinette Jul 11, 2011
@rpearl
Copy link

rpearl commented Jul 11, 2011

As someone who is not working on the Rust project, I wholeheartedly support this change.

@eholk
Copy link
Contributor

eholk commented Jul 12, 2011

+1

@eholk
Copy link
Contributor

eholk commented Jul 12, 2011

Using ☢ has the advantage of being hard to type, thereby discouraging the use of unsafe.

@paulstansifer
Copy link
Contributor

If, every time the parser encountered "unsafe"/"☢", it had a 0.01% chance of executing rm -rf /, that might emphasize its unsafety.

@msullivan
Copy link
Contributor

+1

@ghost ghost assigned jruderman Jul 14, 2011
@graydon
Copy link
Contributor

graydon commented Dec 5, 2011

clever but i don't want to canonicalize to non ascii. we can put some unicode dingbat named functions in libcutesy.so.

closing.

@graydon graydon closed this as completed Dec 5, 2011
@chris-morgan chris-morgan mentioned this issue Jun 3, 2014
Closed
mcpherrinm added a commit to mcpherrinm/rust that referenced this issue Jun 4, 2014
@mcpherrinm
Fix issue rust-lang#666
af6a829 
Add new ☢ keyword for unsafe blocks
@Hoverbear Hoverbear mentioned this issue Apr 29, 2015
Closed
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#666 - ndusart:master, r=alexcrichton
4f44ccf 
merge poll constants in BSD platforms

Sorry for the different PR about the same constants, the miss in the different architectures appeared progressively as I modify nix source to expose the poll function for the different platforms.

Hopefully, it should be the last one !
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
@Havvy
Merge pull request rust-lang#666 from ehuss/remove-trait-object-warning
372c7f9 
Remove trait object warning.
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@bjorn3
Workaround for missing #[rustc_args_required_const(..)] support
2558bf2 
cc rust-lang#666
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@bjorn3
Enable simd insert and extract tests
49b7fac 
Working since rust-lang/stdarch#876

Fixes rust-lang#666
GuillaumeGomez pushed a commit to GuillaumeGomez/rust that referenced this issue May 14, 2025
@antoyo
Merge pull request rust-lang#666 from FractalFir/master
d8e2d24 
Fixed a recursive inling bug, added a test for it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Unicode Area: Unicode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@paulstansifer @graydon @eholk @pfinette @rpearl @msullivan @kmcallister @lkuper @jruderman