Add Go Concurrency paper by Tu, et al.

hwayne / awesome-cold-showers

For when people get too hyped up about things

Other

7.26k stars 82 forks source link

Add Go Concurrency paper by Tu, et al. #18

Closed technosophos closed 4 years ago

technosophos commented 4 years ago

[X] I have followed the code of conduct.
[X] I have followed the contributing guidelines and used the proper item format.
[X] This is not a duplicate.
[X] The resource is free.
[X] The resource is rigorous because: (please list) It is an academic journal article published in ASPLOS 2019.
[X] The resource is not obnoxious, condescending, etc.
[X] My writup is respectful of both sides.
[X] I've added reasonable caveats.
[X] I've noted if the resource is a video, pdf, etc.

hwayne commented 4 years ago

Could you make the title Understanding Real-World Concurrency Bugs in Go? I should probably add that to the checklist. Also, an important caveat to the paper is that the types of bugs seen with channels and shared memory are different. Channels lead to more blocking bugs (deadlocks, dangling channels) while shared-memory lead to more nonblocking bugs (race conditions, dirty reads).

technosophos commented 4 years ago

Sure! So is the idea that the header is the title of the paper? I didn't pick up on that, but it totally makes sense.

technosophos commented 4 years ago

I added your suggestion verbatim, as I liked the way you worded it.

hwayne commented 4 years ago

Thank you!