Alexander Kuklev
08/12/2025, 11:53 PMjoseph_ivie
08/13/2025, 3:19 PMHunter
08/17/2025, 5:16 AMquery
"type" (not sure what to call it) in the second proposal would be very interesting, and I can see definite applications for some unique quantum computing framework support in kotlin, which would be very cool.
2. The dependency injection proposal, as it stands, seems hard to follow and too niche. I don't like the idea of seemingly magic and nested default parameters, and it doesn't solve the issue of wanting to share a singleton object across an application. What if, instead, there was something like a lateinit object
, similar to a lateinit var
. It's an object with a constructor that must be called before use and can only be called once, otherwise a special error is thrown. This allows users to manually specify their dependencies on startup, or provide a default.