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

Some solution to the "no-value" value, #67

Open
spdegabrielle opened this issue Jul 22, 2019 · 1 comment
Open

Some solution to the "no-value" value, #67

spdegabrielle opened this issue Jul 22, 2019 · 1 comment

Comments

@spdegabrielle
Copy link
Sponsor Member

Some solution to the "no-value" value, which could be such a blessed value, or it could be a way to say that some function accepts all the keywords as some other function. (Possibly related to the above, of course.)

from Wishlist of backwards incompatible things for a future Racket2. #33

@gus-massa
Copy link

Currently unsafe-undefined is used under the hood for this task. See racket/racket@662a902
That helps with some optimizations. I'm not sure if it is good to make this official or create another magic value.

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

No branches or pull requests

2 participants