6 ms·
But not in Rust. Go isn't exactly a bastion of safety. It's memory safe due to the GC, but it has a weak type system, so logic bugs are not well guarded against
by nicoburns 7y ago
But not in Rust. Go isn't exactly a bastion of safety. It's memory safe due to the GC, but it has a weak type system, so logic bugs are not well guarded against.
- zozbot234 7y ago> It's memory safe due to the GC That gets debatable as soon as you start using concurrency, like I said. There are idiomatic patterns in concurrent Go that are very much not safe.
- MaxBarraclough 7y agoWhat do you mean? It has a GC, right? So use-after-free is impossible, no?
- petjuh 7y agoSerious question - has that been verified, especially with regards to concurrency? Also does it rely on the assumption that GC implementions such as Java's are bug-free in this regard, and if so - has that been verified as well?
- lima 7y agoOn the other hand, Go code is a lot easier to audit. The kind of logic bug that the Rust compiler prevents due to stronger typing is typically a crash in Go, not a security issue.
- nicoburns 7y agoDisagree on this. In Rust I can read most of the information I need to know straight from the function signatures. In Go I have to go through every line of code (and there are often a lot of lines due to Go's lack of expressive power).
- lima 7y agoIn Rust code I audit, I typically have to jump through multiple layers of abstraction and cleverness, while Go code is straight forward and boring.
- nicoburns 7y agoI guess it's a matter of preference. If something is abstracted, then you only have to audit it once (and often you can count on someone else having audited it). With Go code, everything is new and unique, so there are a lot more opportunities to introduce bugs.
- Quekid5 7y agoNot to be argumentative, honestly, that sound pretty laughable if you don't have an equivalent of an algebraic effect system (or similar). A "function" in Rust can do a whole bunch of stuff that is not signaled by its type signature.
- nicoburns 7y agoMutability / immutability is in the function signatures, and that goes a long way. It's not as good as an effect system of course. But along with global variables barely being a thing in Rust, it goes a long way to cutting out the common course of bugs.
- Thaxll 7y agoRust is not safer than Go, people thinking otherwise misunderstand borrow checker vs GC. Furthermore you're talking about memory safety vs business logic bugs, two different things.
- pcwalton 7y agoGo is not memory-safe in the presence of concurrency. Interfaces and slices (i.e. fat pointers) are not written atomically, which can cause undefined behavior. I haven't heard of this causing a problem in practice, though.
- Thaxll 7y agoI never heard undefined behavior in Go like your example. This would means that not synchronizing a slice would lead to memory corruption. Please give us a code example.
- skybrian 7y agoSlice values are normally copied so it's not an issue. The slice would need to be stored in a global or a struct's field and then changed while some other goroutine is reading it. (I haven't seen this happen, though.)
- pcwalton 7y agoYes, not synchronizing a slice can lead to memory corruption in Go.
- staticassertion 7y agoHere you go: https://blog.stalkr.net/2015/04/golang-data-races-to-break-memory-safety.html https://blog.stalkr.net/2015/04/golang-data-races-to-break-m... What's even worse is that Go code is not (outside of Linux/ some distros) compiled with ASLR.
- psanford 7y agoHere's a blog post from Russ Cox (Go core team) explaining it: https://research.swtch.com/gorace https://research.swtch.com/gorace