Closed BrookFeleke closed 1 week ago
@BrookFeleke why can't you refactor the usage of
getGuardSetExp
in thezero constraint subsumption
too like you did in thedelete Inconsistent handle
? Then remove thegetGuardSetExp
and change the name of your function to that?
I have made the requested changes and removed the old getGuardSetExp
.
Hey @BrookFeleke, just merged another PR and your code isn't working all of a sudden. I believe it a simple conflict that can be resolved on your side.
Hey @BrookFeleke, just merged another PR and your code isn't working all of a sudden. I believe it a simple conflict that can be resolved on your side.
Yes @Yagth it was because the new isConsistentExp
was using the older version of getGuardExp
with 3 arguments, i have changed that and it passes all tests now.
Description
I have added a new refactored version of the
getGuardSetExp
namedgetGuardSetExpression
that usessuperpose
to increase performance and run in parallel. The new function is I haven't removed the old function since it is used in the modulezero-constraint-subsumption.metta
.Motivation and Context
How Has This Been Tested?
Types of changes
Checklist: