-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
require/untyped-contract leads to errors in no-check, Shallow, and Optional #1286
Comments
Ideas:
|
Hi @bennn , I have posted some seemingly working code to add a language specification to
Best, |
This issue has been mentioned on Racket Discussions. There might be relevant details there: https://racket.discourse.group/t/replacing-lexical-context-in-a-macro/2004/1 |
Yes, language spec should be optional. Fetching automatically seems too hard. It may have trouble with identifiers that get reprovided by TR languages (Shallow -> Deep -> require/untyped-contract). |
I'm confused now. Does it even make sense to use (It doesn't make sense for no-check because that language doesn't generate contracts at all.) Maybe the right thing is just a better error message. |
What version of Racket are you using?
Welcome to Racket v8.6.0.9 [cs].
What program did you run?
This program is ok with normal TR and not okay for shallow, optional, and no-check
server.rkt
main.rkt
What should have happened?
No error
If you got an error message, please include it here.
Shallow
no-check
PS thanks to @Rscho314 for the report in racket/math#75
The text was updated successfully, but these errors were encountered: