...perhaps by passing a kwarg to transform!, or having a transform_free_memory or something?
Right now, the NoThrowDag transform keeps track of all intermediate outputs; since it knows up front what values/fields from each of those outputs will be used downstream, a lighter-weight implementation could only keep those required fields, rather than keeping around any potentially heavy-weight intermediates.
...perhaps by passing a kwarg to
transform!, or having atransform_free_memoryor something?Right now, the NoThrowDag transform keeps track of all intermediate outputs; since it knows up front what values/fields from each of those outputs will be used downstream, a lighter-weight implementation could only keep those required fields, rather than keeping around any potentially heavy-weight intermediates.