Sure, but it’s also a balancing act. We get an enormous explosion of boilerplate in field definitions, as you now have to: 1) define a request type (so that subclasses still work) 2) define a result type, unless there is already a natural result like

Addresses

3) write a rule And it makes call sites much more complex.

from pants.backend.python.target_types import EntryPoint, HydrateEntryPointRequest, HydratedEntryPoint

await Get[HydratedEntryPoint](HydrateEntryPoint(tgt.get(EntryPoint))
print(hydrated_entry_point.value)

vs.

from pants.backend.python.target_types import EntryPoint

print(tgt.get(EntryPoint).value)