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
Sometimes it is useful to write "lenient" specifications, for instance:
return (any [c | c <- connections, c.writeable])
Cozy currently requires all specifications to be fully precise, in the sense that there is only one correct return value. This restricts how efficient its solutions can be when there are multiple possible correct answers and one answer is easier to compute than another.
One possible design that I endorse:
a function to_relational_form that converts any expression into a relation that describes its set of legal outputs
synthesis in core.py should be updated to use to_relational_form when checking correctness
The text was updated successfully, but these errors were encountered:
Sometimes it is useful to write "lenient" specifications, for instance:
Cozy currently requires all specifications to be fully precise, in the sense that there is only one correct return value. This restricts how efficient its solutions can be when there are multiple possible correct answers and one answer is easier to compute than another.
One possible design that I endorse:
to_relational_form
that converts any expression into a relation that describes its set of legal outputscore.py
should be updated to useto_relational_form
when checking correctnessThe text was updated successfully, but these errors were encountered: