News for hackers. Stuff that matters.
Re:Tokio 1.0 – async runtime for Rust by lmm on Thursday December 24, 2020 @09:09PM (#25533561)
> Unless you start writing code that looks like actor based concurrency, with channels used to pass messages acrross actors. But this isn’t what i’d call idiomatic go.

Isn't that exactly what Go people push? "Don't communicate by sharing memory; share memory by communicating" and all that. If you start pushing pointers to shared memory around then I'd expect all of the problems of traditional multithreading to reappear.

Re:Tokio 1.0 – async runtime for Rust by zozbot234 on Friday December 25, 2020 @10:06AM (#25536847)
Passing pointers to shared memory is highly unsafe in Go. While the Rust borrow checker will prevent all data races, there's nothing like that wrt. Go.
Re:Tokio 1.0 – async runtime for Rust by sagichmal on Friday December 25, 2020 @11:09AM (#25537211)
> Passing pointers to shared memory is highly unsafe in Go. While the Rust borrow checker will prevent all data races, there's nothing like that wrt. Go

Passing pointers to shared memory is the foundation of a huge number of idiomatic, performant, and productive design patterns and architectures. There exist a number of conventions and tools, like the race detector, which reduce the risks of data races to entirely reasonable levels.