Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SharedTerm and Recognizer differ on what a tuple is #1383

Open
eddywestbrook opened this issue Jul 20, 2021 · 0 comments
Open

SharedTerm and Recognizer differ on what a tuple is #1383

eddywestbrook opened this issue Jul 20, 2021 · 0 comments
Labels
subsystem: saw-core Issues related to the saw-core representation or the saw-core subsystem type: bug Issues reporting bugs or unexpected/unwanted behavior

Comments

@eddywestbrook
Copy link
Contributor

The functions scTuple, scTupleType, etc. in SharedTerm.hs build tuple types (tp1, ..., tpn) as right-nested pair where the last two types become their own pair type, while the recognizer functions asTupleValue, asTupleType, etc. in Recognizer.hs seem to expect the last type to be paired with a unit type on the right.

That is, the former converts (tp1, ..., tpn) to (tp1, (tp2, ... (tpn-1, tpn) ... )) whereas the latter seems to be looking for something of the form (tp1, (tp2, ... (tpn-1, (tpn, #())) ... )).

@brianhuffman brianhuffman added the subsystem: saw-core Issues related to the saw-core representation or the saw-core subsystem label Aug 3, 2021
@robdockins robdockins added the type: bug Issues reporting bugs or unexpected/unwanted behavior label Aug 13, 2021
@robdockins robdockins self-assigned this Aug 13, 2021
@robdockins robdockins removed their assignment Sep 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subsystem: saw-core Issues related to the saw-core representation or the saw-core subsystem type: bug Issues reporting bugs or unexpected/unwanted behavior
Projects
None yet
Development

No branches or pull requests

3 participants