A modern programming language that makes developers happier.

kotlinlang

I'm not sure if this has been fixed (I believe so tho in 2.x), but I stumbled upon a subtle bug in 1.9.24.
If you have a stateless `object` (only pure functions, no properties), the object is instantiated eagerly thanks to an optimization (which is good for perf!).
However, if that stateless object is used by an `@EagerInitialization`-ed property, there will be a runtime error, as the property is initialized before the optimized `object`.

I remember I fix such a thing in some of the latest releases (2.1.*) maybe

At some point I recall I complained about the `object` optimization not being there anymore, is that maybe what you did?

Yup, KT-70778, you wrote

&gt; Preventive steps taken. The problem was fixed by changing the order of initialization (moving eagerly initialized properties, after the trivial objects initialization), and the test for the case also was added.