-
Notifications
You must be signed in to change notification settings - Fork 156
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
caseCon introduces free variables because of evaluator changes #2623
Comments
leonschoorl
added a commit
that referenced
this issue
Dec 12, 2023
leonschoorl
added a commit
that referenced
this issue
Dec 12, 2023
2 tasks
martijnbastiaan
pushed a commit
that referenced
this issue
Feb 27, 2024
martijnbastiaan
pushed a commit
that referenced
this issue
Feb 27, 2024
martijnbastiaan
pushed a commit
that referenced
this issue
Feb 27, 2024
…2624) (#2681) Fixes #2623 (cherry picked from commit 0aa341a) Co-authored-by: Leon Schoorl <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When compiled with
-fclash-debug-invariants
(DebugSilent
or higher) this crashes with:The problem is that since Give evaluator acces to inscope let-bindings #2571 the evaluator has access to the let bindings, and they may reference new free variables.
In this case it looks like:
The evaluator transforms this into some transformed form of
x
which containsds
, and thencheckDebug
complains there is now a new free variable in the expression:ds
The text was updated successfully, but these errors were encountered: