.@tqbf case precedent for people who don't understand Go's memory model: https://inconshreveable.com/07-08-2014/principles-of-designing-go-apis-with-channels/ …
-
-
Replying to @bascule1 reply 0 retweets 0 likes
-
Replying to @rantyben4 replies 0 retweets 0 likes
-
Replying to @rantyben
@rantyben@bascule https://gobyexample.com/mutexes shared heap, GC, no concept of memory ownership => classic multithreading problems1 reply 0 retweets 0 likes
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.