On Monday, 2 December 2024 at 21:55:55 UTC, Richard (Rikki)
Andrew Cattermole wrote:
As a type qualifier/storage class, ``shared`` should be called
``atomic``.
`shared` is more accurate. Atomic ops are not the only way
intended to mutate `shared` data. In fact atomic ops can be
slower.
If you use it to indicate anything other than the variable can
only be accessed/mutated via atomic operations, you are at best
lieing to yourself about the native memory model.
All memory is owned by the process, until proven otherwise.
Which is the exact opposite of what ``shared`` implies.
`shared` - shared (i.e. accessible) across threads.
