nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-22 06:44:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Reword 'stupid' and 'crazy' in docs.

Browse Source
This commit is contained in:
Clar Charr 2017-01-02 15:47:00 -05:00
parent df61658c8a
commit 8ffc3e7790
5 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
configure vendored
View File

@ -1568,7 +1568,7 @@ do
then then
LLVM_BUILD_DIR=${CFG_BUILD_DIR}$t/llvm LLVM_BUILD_DIR=${CFG_BUILD_DIR}$t/llvm
LLVM_INST_DIR=$LLVM_BUILD_DIR LLVM_INST_DIR=$LLVM_BUILD_DIR
# For some crazy reason the MSVC output dir is different than Unix # For some weird reason the MSVC output dir is different than Unix
if [ ${is_msvc} -ne 0 ]; then if [ ${is_msvc} -ne 0 ]; then
if [ -n "$CFG_DISABLE_OPTIMIZE_LLVM" ] if [ -n "$CFG_DISABLE_OPTIMIZE_LLVM" ]
then then

8
src/doc/nomicon/atomics.md
View File

@ -24,10 +24,10 @@ exactly what we said but, you know, fast. Wouldn't that be great?
# Compiler Reordering # Compiler Reordering
Compilers fundamentally want to be able to do all sorts of crazy transformations Compilers fundamentally want to be able to do all sorts of complicated
to reduce data dependencies and eliminate dead code. In particular, they may transformations to reduce data dependencies and eliminate dead code. In
radically change the actual order of events, or make events never occur! If we particular, they may radically change the actual order of events, or make events
write something like never occur! If we write something like
```rust,ignore ```rust,ignore
x = 1; x = 1;

2
src/doc/nomicon/meet-safe-and-unsafe.md
View File

@ -22,7 +22,7 @@ Well, Rust *has* a safe programming language. Let's step back a bit.
Rust can be thought of as being composed of two programming languages: *Safe Rust can be thought of as being composed of two programming languages: *Safe
Rust* and *Unsafe Rust*. Safe Rust is For Reals Totally Safe. Unsafe Rust, Rust* and *Unsafe Rust*. Safe Rust is For Reals Totally Safe. Unsafe Rust,
unsurprisingly, is *not* For Reals Totally Safe. In fact, Unsafe Rust lets you unsurprisingly, is *not* For Reals Totally Safe. In fact, Unsafe Rust lets you
do some really crazy unsafe things. do some really, *really* unsafe things.
Safe Rust is the *true* Rust programming language. If all you do is write Safe Safe Rust is the *true* Rust programming language. If all you do is write Safe
Rust, you will never have to worry about type-safety or memory-safety. You will Rust, you will never have to worry about type-safety or memory-safety. You will

10
src/doc/nomicon/races.md
View File

@ -21,11 +21,11 @@ prevent *all* race conditions would be pretty awful to use, if not just
incorrect. incorrect.
So it's perfectly "fine" for a Safe Rust program to get deadlocked or do So it's perfectly "fine" for a Safe Rust program to get deadlocked or do
something incredibly stupid with incorrect synchronization. Obviously such a something nonsensical with incorrect synchronization. Obviously such a program
program isn't very good, but Rust can only hold your hand so far. Still, a isn't very good, but Rust can only hold your hand so far. Still, a race
race condition can't violate memory safety in a Rust program on condition can't violate memory safety in a Rust program on its own. Only in
its own. Only in conjunction with some other unsafe code can a race condition conjunction with some other unsafe code can a race condition actually violate
actually violate memory safety. For instance: memory safety. For instance:
```rust,no_run ```rust,no_run
use std::thread; use std::thread;

2
src/libstd/sys/windows/thread_local.rs
View File

@ -207,7 +207,7 @@ unsafe fn unregister_dtor(key: Key) -> bool {
// loop to basically match Unix semantics. If we don't reach a fixed point // loop to basically match Unix semantics. If we don't reach a fixed point
// after a short while then we just inevitably leak something most likely. // after a short while then we just inevitably leak something most likely.
// //
// # The article mentions crazy stuff about "/INCLUDE"? // # The article mentions weird stuff about "/INCLUDE"?
// //
// It sure does! Specifically we're talking about this quote: // It sure does! Specifically we're talking about this quote:
// //