News for hackers. Stuff that matters.

A comment on Rust 1.17. Parent comment

Re:Rust 1.17 by steveklabnik on Friday April 28, 2017 @03:24AM (#14217516)
Go, in my understanding, is not memory safe even with its gc, and also doesn't have "concurrency safety" because of this. That's why https://golang.org/doc/articles/race_detector.html exists.

Rust however prevents these kinds of errors at compile time.

Which things were you thinking of that Rust was lacking here?

[ Parent | on HN ]
Re:Rust 1.17 by rurban on Friday April 28, 2017 @06:52AM (#14218357)
The go race detector is still miles better than enforcing manual mutexes and locking in concurrent Rust code.

Much better would be a proper type system to get rid of those at compile-time of course. Look at pony. And a better memory-safety system than RC.

[ Parent | on HN ]
Re:Rust 1.17 by steveklabnik on Friday April 28, 2017 @07:25AM (#14218514)
You don't always need those; it depends on what you're doing. And furthermore, that _is_ the compile time system that enforces things. Go's race detector can only prove the presence of things, not their absense.

As for Pony,

> Pony-ORCA, yes the killer whale, is based on ideas from ownership and deferred, distributed, weighted reference counting.

That's it's GC.

[ Parent | on HN ]