Don't use value class Reset with AtomicRef

[DRSchlaubi]

The use of value classes for the Reset class has already caused issues implementing #855. However, it was isolated to native platforms. Unfortunately, this behavior will become a compiler error soon, so we need to change it. This can be achieved by simply using the backing Instant instead of Reset with AtomicRef.

Related Issues

#855
#69
Kotlin/kotlinx-atomicfu#291
KT-61584

[lukellmann]

if we have a breaking change here anyway, do we really need this wrapper around Instant at all?

[DRSchlaubi]

Probably not

[lukellmann]

let me see what i can do then

[lukellmann]

ok, so i kept Reset as an @JvmInline value class, deprecated it and replaced the usages with plain Instant. with some annotation trickery, i think i managed to preserve binary compatibility, so only source compatibility is broken now (which is easier to fix).

[lukellmann]

can you take a look @DRSchlaubi? (can't request an review from you, you are the pr author)

[lukellmann]

wait a second, i just noticed that we don't even have to change any public api, we can just box/unbox the Reset.value internally without api changes

[lukellmann]

simply using the backing Instant should do the job, what do you think @DRSchlaubi?

[DRSchlaubi]

Looks good