3 ms·

That's not laziness, that's just cache invalidation.

• swift 13y ago
  It's fair to say that it's laziness, in my view. That sort of thing is just a manual implementation of what laziness would do in a particular situation. The closure that the thunk would hold is essentially diffused into the object that contains the lazy property.