Hi
On 6/22/24 00:22, Benjamin Außenhofer wrote:
Given the complexities of newLazy* already, i am just trying to find
arguments to keep the public surface of this API as small as posisble, as
its intricacies are hard to grasp and simplicity / less ways to use it will
be a benefit.
So far i don't see that with resetAsLazy* you can impmlement something new
that cannot also be done with newLazy* methods.
For the record, I share these concerns and also mentioned them in the
email that I just sent. I've also previously asked this in this email,
including the named constructor as a workaround, just as Benjamin did:
https://externals.io/message/123503#123525
Best regards
Tim Düsterhus
