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

Behaviour of (letrec ([x x]) x) changed in Racket #103

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

soegaard
Copy link
Contributor

The latest Racket has changed the behaviour of (letrec ([x x]) x).
Currently any program beginning with #lang whalesong fails due
to an "x undefined" error. The undefined value is now exported
from racket/undefined.

The latest Racket has changed the behaviour of (letrec ([x x]) x).
Currently any program beginning with #lang whalesong fails due
to an "x undefined" error. The undefined value is now exported
from racket/undefined.
@soegaard
Copy link
Contributor Author

Note that (letrec ([x x]) x) is used in other files too:

grep -r undefined * | grep letrec
whalesong/cs019/private/sigs-patched.rkt:(define the-undefined-value (letrec ([x x]) x))
whalesong/cs019/teach-runtime.rkt:(define undefined (letrec ([x x]) x))
whalesong/tests/older-tests/moby-programs/misc.rkt:(check-expect (undefined? (letrec ([x x]) x)) true)

@soegaard
Copy link
Contributor Author

Also in kernel.rkt the function -undefined? could be replaced with:
(require racket/undefined)
(define (-undefined? x)
(eq? x undefined))

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.

1 participant