Atomic composition implementations #289
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Experimental! This replaces certain compositions with "atomic" implementations, which means they themselves aren't compositions at all, serving as a complete property descriptor instead. The atomic implementations are strictly in terms of a reference implementation, that being the existing composition which the atomic implementation stands in for.
Notes:
{flags: {compose: true}}
)..outputs({})
system (for renaming outputs) continues to work as intended! We're thinking the neatest way to handle both this point and the one above is basically to factor out the useful behaviors of bothtemplateCompositeFrom
andcompositeFrom
, and employ those in a lighter-weight wrapper - one which always only expects a single compute/transform. However, this needs to be compared - in terms of performance - against just using the existingtemplateCompositeFrom
and creating single-step compositions, which are perfectly well supported already.