I agree wholeheartedly. Use the race detector, and well designed code - much easier to understand and maintain than the equivalent Rust IMO.
> On Mar 4, 2019, at 1:49 PM, Manlio Perillo <manlio.peri...@gmail.com> wrote: > > On Monday, March 4, 2019 at 8:06:16 PM UTC+1, Jeff Kayser wrote: > Paradigms of Rust for the Go developer > https://medium.com/@deckarep/paradigms-of-rust-for-the-go-developer-210f67cd6a29 > > <https://medium.com/@deckarep/paradigms-of-rust-for-the-go-developer-210f67cd6a29> > > I found this article extremely interesting. Concurrency safety appears to be > an area where Rust beats Go. > > > Thanks for the article. > I'm one of the programmers that think Rust is too complex. > > I don't have any intentions to move to Rust. But it would sure be nice if Go > offered the same or similar safety features for concurrency. > > I think Go should offer something like: > https://doc.rust-lang.org/error-index.html > > > [...] > > Manlio > > -- > 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 golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
