Skip to content

Tracking meta issue: parser related changes #11481

@smoothdeveloper

Description

@smoothdeveloper

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

adjustments / 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.

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


@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 🙂

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    New

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions