3 ms·
>>Haskell is pretty much the counter example. I said "very often" for this reason, there is always an exception to the rule. I do love Haskell too. >>This is
by voidlogic 13y ago
>>Haskell is pretty much the counter example.
I said "very often" for this reason, there is always an exception to the rule. I do love Haskell too.
>>This is why I am far more exited by Rust than by Go, it promises to deliver performance and safety in an imperative language.
To be clear we were talking about concurrency safety, not type and memory safety; Go is type and memory safe. If an organization using Go chose to tell programmers they could not send pointers between goroutines or share global state, Go would be just as communication safe as Rust. Just in Go, this communication safety is optional.
- pcwalton 13y ago> To be clear we were talking about concurrency safety, not type and memory safety; Go is type and memory safe. Not if you're using parallelism (GOMAXPROCS > 1). > If an organization using Go chose to tell programmers they could not send pointers between goroutines or share global state, Go would be just as communication safe as Rust. Just in Go, this communication safety is optional. It is in Rust as well. You just have to declare that you're opting into data races; safety is the default and enforced by the compiler if you don't opt in.