Support Non-blocking Concurrency Primitives #170
Labels
Comments
These should be available for very low-level code, but we hope that most code will be built on top of higher-level, less error-prone primitives like channels. Owner changed to r...@golang.org. Status changed to Accepted. |
@dahankzter: http://golang.org/doc/go_lang_faq.html#atomic_maps |
Java freaks like me are prone to caching and having structures transparently use low level cas instructions for example helps avoiding hand syncing. I think its probably a good idea to skip it (at least initially) since things like this part of why new approaches are needed. |
|
This issue was closed by revision 22eab1f. Status changed to Fixed. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by mikeb01:
It would be useful to have support for operations commonly used with non- blocking concurrency such as volatile reads/writes, compare and set/exchange, and atomic increment. This doesn't need language support, but probably would require support from the runtime. Perhaps something similar to .Net's Interlocked.CompareExchange, Interlocked.Increment, and Thread.Volatile{Read,Write}.The text was updated successfully, but these errors were encountered: