Youssef Shoaib

I got nerd-sniped by this, and have now opened #37 I'll write a neater explanation for my ideas soon, but for now: I have a [project](https://github.com/kyay10/KonTinuity/tree/split-seq) in the works that...

Yeah that intended usage is absolutely fine! It's not even about `EXACTLY_ONCE`-ness. The potential issue is if the code uses mutable state in a presumed-linear way. A simple manifestation of...

Take all the time you need! Feel free to ask any questions or anything like that. FWIW, I'm pretty sure your current implementation is basically a [thermometer continuation](https://calwoo.github.io/posts/2020-02-12-thermometer_p1.html) but specialized...

I want to expand a little more on "why not value class". You mention that the objects will have no identity, but I don't see the issue with that. Couldn't...

I think the atomics should also come with an `assign` method by default that works with the assign plugin

My point about referential equality is that it's unnecessary since normal equality will suffice (it'll compare the underlying references in case of JVM). In other words, I'd expect that `AtomicIntInline(0)...

You mention that "class or top-level properties" cannot be unnamed. This makes sense for class properties, since one can use an `init` block. However, there's no `init` option for the...

You also mention that "Unnamed variables cannot be delegated". I have a very clear use case for this though: triggering `provideDelegate` without using the resulting delegate object. An almost-example of...

My bad, what I had in mind was `getting` I believe because it's used for configuration quite often. Again, in Gradle this doesn't actually make much sense because of the...

I agree with @CLOVIS-AI. Maybe, in the future, state 3 can be the default if someone has `explicitApi` turned on?