[concurrency-interest] Problems understanding "visibility"

Chris Purcell chris.purcell.39 at gmail.com
Wed Oct 19 14:37:46 EDT 2005

I'm having problems understanding this word "visibility" that keeps 
getting used. Is it possible to create a concurrent program that can 
actually tell the difference between acquire/release having only 
ordering constraints, and acquire/release having ordering + visibility 
constraints? Moreover, what concurrent design idioms require visibility 
for correctness?


More information about the Concurrency-interest mailing list