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
******************** testing ./forge-core/examples/booleanLogic.rkt
uncaught exception: "Upper bound too large for given BitWidth; Sig: #(struct:Sig Formula (relation 1 "Formula" (Formula) univ) #f #t #f (Var Not And Or)), Upper-bound: 8, Max-int: 7"
Right now we're always encoding bounds numerically, even when we don't have to.
The text was updated successfully, but these errors were encountered:
@k-mouline As I review our older issues, I'm wondering: is this causing any trouble for our theory-of-relations translation? Sometimes Forge will produce a cardinality constraint on the size of a sig. Alloy does something smarter: it produces a some disj atom0, atom1, ... constraint that has the same effect.
This doesn't seem to be a performance gain in general -- negating the above is slow. Worth looking again into what Alloy does, as they are surely not doing something as inefficient as what I just tried.
E.g.,
******************** testing ./forge-core/examples/booleanLogic.rkt
uncaught exception: "Upper bound too large for given BitWidth; Sig: #(struct:Sig Formula (relation 1 "Formula" (Formula) univ) #f #t #f (Var Not And Or)), Upper-bound: 8, Max-int: 7"
Right now we're always encoding bounds numerically, even when we don't have to.
The text was updated successfully, but these errors were encountered: