Conversation

Go has GC and Rust doesn't. If you were to design an explicitly C-like language with memory safety and without GC, it would look a lot more like Rust than Go. The idea that Rust was designed by a bunch of C++ fans is absurd. Most of us were ML fans more than anything. t.co/SWJhLJptY3

This Tweet is unavailable.

238

This Tweet was deleted by the Tweet author. Learn more

Patrick Walton

@pcwalton

Jul 25, 2019

The issue is that generics are basically a requirement for memory safety without GC as Rust does it. Otherwise you can't create safe abstractions, which would mean that every time you want a linked list you have to write unsafe code. That would undermine memory safety.

This Tweet was deleted by the Tweet author. Learn more

Daniel Micay

@DanielMicay

Go is only memory safe if you force the runtime to use a single OS thread. It's not memory safe by default. It doesn't pay the price of providing safety in the presence of data races like Java. The built-in map and slice types don't maintain memory safety during data races.

8:18 PM · Jul 25, 2019Twitter Web App

Replying to

and

It's both garbage collected and memory unsafe. If you think this isn't a real world issue and couldn't be exploited, you would be very wrong. The approach it takes makes data races common: pass-by-reference for mutable data structures that are memory unsafe when races occur.

Replying to

I’ve had famous security people tell me that there is no way that issue could be exploited. I was skeptical but I was willing to concede the point at the time 🤷‍♂️

Show replies