The only thing I don't like is its name. I don't l...
# coroutines
e
The only thing I don't like is its name. I don't like neither
fun asyncLazy
nor
interface AsyncLazy
, because it is not really async in the same sense as people are used to this word in JS/C#/Dart. It does not have any futures or promises in there. Consider, for example, the following declaration:
Copy code
val v = asyncLazy { ... blah-blah .. }
Now if I actually need a future that completes when
v
is computed, then I'd write:
Copy code
val futureV = async { v.value() }
So, calling
v
itself as async-something is a misnomer, because to get a future I'll have to use
async
builder on it. How can it be named better? (the same naming problem applies to other examples we currently have in coroutines KEEP)