@bascule You are on tilt about this issue and it makes you sound silly.
-
-
-
@tqbf I think there's a common misconception that Goroutines have isolated heaps and I'd like to correct that -
@bascule NOBODY has that misconception. -
@tqbf I beg to differ -
@bascule Well, it’s a “common” misconception; should be no trouble to provide some links. -
@tqbf it's hard to link to IRC conversations -
@bascule Thought so. -
@tqbf I'm serious though, I've talked to many people who are surprised to learn that goroutines share state - 4 more replies
New conversation -
-
-
.
@bascule wait what, a Go program [without raw pointer access] can just go and segfault? WTF. -
@whitequark that would be a different type of memory safety ;) -
@bascule referring to the part where internal structures aren't protected. Intertwine reading/resizing an array → access to stale memory! -
@whitequark yeah. All immutable all the time is one solution. Rust's region typing is an attractive alternative for shared mutable state -
@bascule what if you have an array of pointers and a collection happens between two goroutines run? -
@whitequark@bascule one cannot simply invent high-level memory safety without building a full-blown VMM -
@0xABD@whitequark or a sufficiently smart compiler -
@bascule@whitequark ...until you realize you had better run your code on a bare metal hypervisor to get rid of all those extra layers. - 1 more reply
New conversation -
-
-
@bascule LUA isolates their state correctly. :)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.