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

Fix tracking which branches are already true or false in conditionals #56

Merged
merged 6 commits into from
May 26, 2018

Conversation

quasicomputational
Copy link
Collaborator

Previously, only one list of already-seen conditions was kept, and
this was assumed to be the list of 'true' conditions. But that was
also being added to in the false branch! We actually need to keep two
lists, one of already-true and one of already-false.

Fixes #53. Fixes #55.

quasicomputational and others added 5 commits May 21, 2018 11:25
Previously, only one list of already-seen conditions was kept, and
this was assumed to be the list of 'true' conditions. But that was
also being added to in the false branch! We actually need to keep two
lists, one of already-true and one of already-false.

Fixes dhall-lang#53. Fixes dhall-lang#55.
Since these are represented specially in Cabal's CondTree type, this
is worth testing explicitly.
@ocharles
Copy link
Member

Perfect! Thank you for adding tests, and good job understanding what the hell this code does!

@ocharles ocharles merged commit 251fbc9 into dhall-lang:master May 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants