News for hackers. Stuff that matters.

A comment on Uber Go Style Guide. Parent comment

Re:Uber Go Style Guide by sanxiyn on Friday October 11, 2019 @12:25PM (#21225860)
Shared mutable state is evil, so "not mutable" has been proposed as a solution. Rust is different, because Rust's solution is "not sharing". You can still mutate!
[ Parent | on HN ]
Re:Uber Go Style Guide by reificator on Friday October 11, 2019 @12:49PM (#21226097)
> Rust is different, because Rust's solution is "not sharing". You can still mutate!

For the record, rust does also default to immutability, and you can share immutable references all you'd like.

[ Parent | on HN ]
Re:Uber Go Style Guide by bcrosby95 on Friday October 11, 2019 @04:21PM (#21228085)
I would describe Rust more like a read-write lock than not sharing.
[ Parent | on HN ]
Re:Uber Go Style Guide by nine_k on Saturday October 12, 2019 @12:25PM (#21234311)
A lock is acquired and detected at runtime.

Ownership and move semantics are checked at compile time, and allow effective "not sharing" without waiting or defensive copies.

[ Parent | on HN ]