Yeah, Lazy should have been deprecated and removed, I simply did not have time to bother.
That’s because the library is not about calculated values (btw, they are truly calculated, not dynamic defaults; when any of values it depends on has changed, the value in calculated field(s) is also re-calc’ed.)
This library is about handy generation od property-data for property-based testing in the first place, it just supports calculated values by accident.
I am not sure how would you expect dependencies to automagically convert to support dynamic defaults, let alone it might break them. For a big production project, I would typically comment out the declaration of the struct, collect all compilation errors, and fix them one by one. Changing them to a constructor would probably suffice your needs, but I might be mistaken.
