Make fields nested inside a data type from template parameters available for autowiring/autobinding in choice scope

TBQH it is less devilish than .. in record-creation; introducing a bunch of bindings seems much less scary to me than automatically using whatever bindings are laying around. Certainly one of the unstated reasons I posted about using records more was to encourage a Daml style that wouldn’t lean so heavily on .. record creation.

Then again I come from the “DI is useless, just pass arguments to a function” school of thought.

@meet On a more serious note, if the same set of fields happens to be used in several places, it may be clearer to factor that set of fields to a record, and then pass it explicitly. Of course that totally depends on the other code details not seen here.

2 Likes