Great! I liked Mill's lecture. After having seen it, here's my favourite:
*Clojure core.async*, lecture (45 mins). Rich Hickey discusses the
motivation, design and use of the Clojure core.async library. He also talks
about go. See https://www.infoq.com/presentations/clojure-core-async/
(lecture
On Friday, 27 November 2020 at 10:32:11 UTC oyvin...@teigfam.net wrote:
> Thread safety, concurrency safety, goroutines safety. The same stuff to
> me.
>
> It's important that concurrent goroutines don't interfere with each other
> in such a way that internal state is compromised by other goro
Thread safety, concurrency safety, goroutines safety. The same stuff to me.
It's important that concurrent goroutines don't interfere with each other
in such a way that internal state is compromised by other goroutines.
Typically through access to internal data, through pointers. If only go
On Wed, Nov 25, 2020 at 6:13 PM Alexey Dvoretskiy
wrote:
>
> How would you cal "thread-safety" in Go? Go doesn't have threads so the term
> "thread-safety" sounds bit off.
The standard library says things like "Multiple goroutines may invoke
methods on a Conn simultaneously" (from
https://golang
On Wed, Nov 25, 2020 at 6:13 PM Alexey Dvoretskiy <
advorets...@emeraldcloudlab.com> wrote:
> How would you cal "thread-safety" in Go? Go doesn't have threads so the
> term "thread-safety" sounds bit off.
Some more context around your question would be helpful. Personally, I
don't see a problem
How would you cal "thread-safety" in Go? Go doesn't have threads so the
term "thread-safety" sounds bit off.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gola
