Okay. Generally, with this project, I’m trying very hard to avoid premature abstractions. It sounds like

LazyField

is very likely premature. Maybe we end up finding that it is worth adding back, but for now, it’s more complexity than necessary. We should only add it when we find there’s a compelling use case So, I will change

PrimitiveField

to now eagerly compute its

.value

, rather than it being a property For the original

Address

problem, this solves things. We pass the

Address

to the constructor of

PrimitiveField

so it can access it for any validation errors, but then the field will throw it away after. For

AsyncField

, we will store

Address

as a field that can be accessed upon lazy hydration