- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 93
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
racket/class methods are always annotated as "no bound occurrences" #369
Comments
Do we want an arrow for
If the answer is yes, then perhaps a solution is to add a new kind of syntax property, like If the answer is no, then I think we can simply change the |
Hmm.
reports that So I think there are two bugs here.
|
For point 2 above, I think it might be fixable inside check syntax. If so, the fix would be some where in this general vicinity. It may be that the argument ( |
As discussed here: greghendershott/racket-mode#440
As with #366 I'm not sure if this can/should be fixed in
drracket/check-syntax
as opposed to the source e.g.racket/class
.The text was updated successfully, but these errors were encountered: