re: “storing an Address on the field” , if we fixed https://github.com/pantsbuild/pants/issues/7490 , you could project them both as separate params

That won’t help unless we make you use the engine to hydrate every single field. For 95% of fields, you simply call

my_tgt.get(Compatibility).value

, i.e. Pure Python with no engine. That is very intentional to avoid needing to use the engine for accessing something as simple as a boolean field

zip_safe

. See https://github.com/pantsbuild/pants/pull/9284#discussion_r391817323 for more on why I think we really really want to avoid always using

AsyncField

and should preserve

PrimitiveField