Regarding the intersection of type restriction and atomicity

[Quân Anh Mai]

Hi,

An anomaly I notice in the design docs is that an exclamation on non-atomic
trivially constructible value types may signify both non-nullability and
non-atomicity, which may be different from the mark on other types, which
only denotes non-nullability. This may create headache, what if we want a
non-nullable Complex but still want the variable to be updated atomically.
I propose that we can use a double exclamation mark to not overload the
single one with accidental purposes.

Regards,
Quan Anh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/valhalla-spec-comments/attachments/20230601/58919db2/attachment.htm>