Support for "only store is exclusive" atomic variables

[oakad]

Description

A rather common pattern in concurrent code is a use of atomic variable, that can be read outside of locked section but must be modified only inside the locked section. Examples of such usage are quite plentiful both in Go runtime and elsewhere in application software (one of the simplest such examples is implementation of sync.Once).

It will be very helpful is such use of atomic variables with locks could be expressed in checklocks annotations.

Is this feature related to a specific bug?

No response

Do you have a specific solution in mind?

No response