README: improve description

[tshepang]

• I assume multithreaded meant thread safety
• significant felt a bit heavy

[rust-highfive]

r? @pcwalton

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

[arielb1]

We don't guarantee thread-safety (what with it being often a problem-domain issue). We do however make usage of threads easy, and race conditions mostly opt-in.

[tshepang]

@arielb1 interesting... I got the thread safety bit from the Rust website:

Rust is a systems programming language that runs blazingly fast, prevents nearly all segfaults, and guarantees thread safety.

[steveklabnik]

There's another open ticket about changing that, because it's too
over-reaching, and doesn't have a great definition to begin with.

On Wed, Jun 17, 2015 at 5:32 PM, Tshepang Lekhonkhobe <
[email protected]> wrote:

@arielb1 https://github.com/arielb1 interesting... I got the thread
safety bit from the Rust website:

Rust is a systems programming language that runs blazingly fast, prevents
nearly all segfaults, and guarantees thread safety.

—
Reply to this email directly or view it on GitHub
#26374 (comment).

[tshepang]

@steveklabnik which repo is the ticket at?

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

#26215

[steveklabnik]

oh my, my conf wifi is spotty and so sent this a zillion times, sorry :(

[tshepang]

fresh PR: #26410
I failed to squash the commits in this one