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

can't use unbound variables - evaluator and stepper time out #1389

Open
cyrus- opened this issue Sep 11, 2024 · 3 comments · May be fixed by #1393
Open

can't use unbound variables - evaluator and stepper time out #1389

cyrus- opened this issue Sep 11, 2024 · 3 comments · May be fixed by #1393
Assignees
Labels
bug critical critical bug

Comments

@cyrus-
Copy link
Member

cyrus- commented Sep 11, 2024

image

@cyrus- cyrus- added bug critical critical bug labels Sep 11, 2024
@cyrus- cyrus- moved this to Team Dynamics in Hazel Big Board Sep 11, 2024
@cyrus-
Copy link
Member Author

cyrus- commented Sep 11, 2024

seems to be an issue specifically when the unbound variable is the same as the function argument variable

@Negabinary
Copy link
Contributor

It's specifically a capture issue

if you do

(fun x -> x)(x)

then it gets stuck in a lookup loop indefinitely because the variable x has value x in the environment. I guess we do need a distinction between bound and unbound variables in the implementation.

@Negabinary
Copy link
Contributor

I think the issue is that, because the $x$ is indet, it needs to be wrapped in its own environment before it gets added to the function's environment.

@Negabinary Negabinary linked a pull request Sep 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug critical critical bug
Projects
Status: Team Dynamics
Development

Successfully merging a pull request may close this issue.

2 participants