read the value stored in this atomic and do not care about synchronization.
In case of concurrent write operations, the result that is read may be outdated. In the presence of concurrent writes and no synchronization, out-of-thin-air values are possible (see https://dl.acm.org/doi/10.1145/3276506).
In general, this is useful only for debugging or monitoring purposes where occasionally wrong random results are acceptable.
0.095dev (2025-08-15 12:02:22 GIT hash 301b5b75e77076d091b38f555473f9f0e31e5b5c built by fridi@fzen)
In case of concurrent write operations, the result that is read may be
outdated. In the presence of concurrent writes and no synchronization,
out-of-thin-air values are possible (see https://dl.acm.org/doi/10.1145/3276506).
In general, this is useful only for debugging or monitoring purposes where
occasionally wrong random results are acceptable.