-
Notifications
You must be signed in to change notification settings - Fork 816
Tracking
meta issue: parser related changes
#11481
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
Comments
@smoothdeveloper the note you have for #11487 can be checked off now :) |
Closed
This was referenced Nov 18, 2021
Closed
This was referenced Oct 1, 2022
Tracking
meta issue: parser related changes
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a (for now) blank issue, with intent of assembling list of issues/enhancement requests around the F# parser. The idea is to have a hub to ease onboarding of contributions to the parser by the community or main stake holders maintaining the language, in similar fashion we have issue #1103.
I'll just put the categories I know of, for now.
error recovery in the parser
those issues are about enabling damage mitigation in case of syntax error, for the tooling to recover and remain usable.
See the "thriller" which is a good intro of current state of things: https://youtu.be/3Zr0HNVcooU?t=4977
of
) breaks the whole filematch
Ident.(
and the tooling doesn't help typing qualified custom operators #16260adjustments / improvements / inconsistencies in the AST
those issues are about making the AST more consistent, and reducing needs of adhoc hacks in tooling to work around some of the historical choices made for the AST representation out of the parser.
__LITERALS__
)extern
functions #12613 (also impacts code gen)error messages to enhance that incur dealing with the parser tokens
those issues are meant as a subset of #1103 when a particular issue has been investigated and identified as "best fixed through change in the parsing".
change to the language
return
and type annotations to play well together without needing parentheses #15788@TIHan, @auduchinok , @nojaf & others, if you have tickets you want me to list here, you can ping me on the slack or elsewhere and I'll bring them up / classify. If there are other categories to add, please let me know.
Hope this serves as useful as our model issue handled by @isaacabraham 🙂
The text was updated successfully, but these errors were encountered: