News for hackers. Stuff that matters.
Re:Go 1.9 is released by artursapek on Thursday August 24, 2017 @07:09PM (#15094860)
It could just be one map shared by many goroutines, which normally causes a panic:

    fatal error: concurrent map writes
Re:Go 1.9 is released by freecodyx on Thursday August 24, 2017 @07:15PM (#15094898)
i am dealing with this problem right now. also i have a big problem with deepclone,

I did a big rewrite of a current project, and clearly it was badly designed :(

Re:Go 1.9 is released by azinman2 on Thursday August 24, 2017 @09:38PM (#15095500)
Standard practice is to use a mutex to guard against concurrent usage.
Re:Go 1.9 is released by logicallee on Thursday August 24, 2017 @11:54PM (#15095987)
also necessary for reads?

Also, do you have any good references to proper best practices around concurrent and parallel programming? (in Go.) Like just basic things. Code I can copy and paste without it having obscure race conditions because that use of mutex is absolutely correct, and something that lets me understand the limitations. I feel like it is very easy to do things "wrong" or not notice some edge cases. In C++ I didn't only ever coded single-threaded for this reason. Too many gotchas. Any help would be appreciated.

Re:Go 1.9 is released by dgellow on Friday August 25, 2017 @01:07AM (#15096258)
I would suggest you to read the book "Concurrency in Go", by Katherine Cox-Budai, 2017: http://shop.oreilly.com/product/0636920046189.do
Re:Go 1.9 is released by logicallee on Friday August 25, 2017 @02:15PM (#15100840)
Thank you for the recommendation!
Re:Go 1.9 is released by carbocation on Friday August 25, 2017 @12:16AM (#15096078)
Necessary for reads unless no additional writing will be done. If you initialize/write into a map and then later have concurrent reads from it, the program will run. If you try to write in the midst of this, it will crash.