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

Create Morphir Parsing Frontend #273

Open
DamianReeves opened this issue Jun 25, 2024 · 1 comment
Open

Create Morphir Parsing Frontend #273

DamianReeves opened this issue Jun 25, 2024 · 1 comment

Comments

@DamianReeves
Copy link
Member

Create Morphir Parsing Frontend

We want to make it easier to add new front-ends to Morphir. One way we are looking at doing this is by creating:

  • A Morphir language dialect (we want to fork one of the tree-sitter parsers for either Elm or Gleam, I'm thinking Gleam)
  • A Morphir AST
  • A way to map other parsers onto the Morphir AST (for example, directly map Elm and/or Gleam onto Morphir)
  • The AST should capture enough info to feed into the type inferencer.

Tech

We can get "free" parsers by leveraging tree-sitter parsers. We want to explore using tree-sitter parsers as a frontend to parsing.

@stephengoldbaum
Copy link
Member

It would be most helpful to understand what functionality this addresses for the community. Are teams considering replacing Elm as their authoring language? How will this help? For those teams, is Gleam any more palatable? Basically, why are we considering doing this?

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