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.

Sign up for GitHub

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

Jump to bottom

Forcing a non-listy value should not result in a value being cached #91

Open
kavigupta opened this issue Apr 5, 2019 · 0 comments
Open

Forcing a non-listy value should not result in a value being cached #91

kavigupta opened this issue Apr 5, 2019 · 0 comments

Comments

@kavigupta
Copy link

It should work exactly like error.

scm> (define x (delay (begin (print 2) (/ 1 0))))
scm> (force x)
2
Error
scm> (force x)
2
Error

but right now it seems to cache the value and not re-evaluate it

scm> (define x (delay (begin (print 2) 0)))
scm> (force x)
2
Error
scm> (force x)
Error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix behavior when promise result is invalid jathak/dart_scheme
1 participant
@kavigupta