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
I realized that while writing the guide. Every usage of memory we have will either do something if there is a decision or something else if there isn't one yet. The only method returning a mix of decision and derivation is assignment_intersection but in fact, if there is a decision, we don't need derivations term, since the intersection will directly be the term of the decision.
So in fact we should have PackageAssignment be an enum instead of a struct. That would imply some changes in the API, and especially some algorithm changes regarding remove_decision that should not be used anymore, but I believe this is doable.
The text was updated successfully, but these errors were encountered:
I realized that while writing the guide. Every usage of memory we have will either do something if there is a decision or something else if there isn't one yet. The only method returning a mix of decision and derivation is
assignment_intersection
but in fact, if there is a decision, we don't need derivations term, since the intersection will directly be the term of the decision.So in fact we should have
PackageAssignment
be an enum instead of a struct. That would imply some changes in the API, and especially some algorithm changes regardingremove_decision
that should not be used anymore, but I believe this is doable.The text was updated successfully, but these errors were encountered: