You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to resolve input mixtures to definite expressions before we start preparing multiset functions. Actually this may be negotiable since the multiset function only needs to know the variable type.
We have to prepare multiset functions so that we can know what detached inputs there are.
Should detaching happen before or after expression preparation?
We need to know the detached inputs are so that we can know what the preferred pop order is.
Initial expression state possibly wants to depend on pop order. Do we do the same prepare() (orderless) - delve.initial_state() (ordered) split as with evaluators?
How can we prevent the information needed in delve.initial_state() from unnecessarily affecting the delve's cache key? For evaluators we used the option of externally-provided kwargs.
With Transmit multiset cardinality through variables? #227 the preferred pop order and initial expression state may also depend on the upstream expressions. Cardinality can't be determined until after mixtures are resolved. Preferred pop order may depend on the availability of cardinality. So here the sequence would have to be mixtures / detach -> cardinality -> pop order -> initial state.
Inner expressions are also currently lacking influence on pop order -- actually, they use eval order. This is interesting; an expression inside a multiset_function looks like any other, so it might be expected to use pop order, though it could also be argued that multiset_function produces an evaluator, which may be expected to use eval order.
None
for generators?inner_inputs
), while the latter more resembles external inputs.MultisetExpressionReady
MultisetDelver
- riffing offMultisetDungeon
The text was updated successfully, but these errors were encountered: