-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fast and correct type parsing written by Elm core team #81
Comments
Looks good. Might help in some areas |
There is unreleased official Elm parser. It is very simple and has different approach than regexow based parsers but may be worth experimenting with. It's utility library for parses and may be useful in some areas as well |
@joonazan that code was recently removed, so the link is broken now. Thanks for sharing though. Here's the relevant commit: |
@brian-carroll Do you know why package.elm-lang.org does not need it anymore? Also, if anyone is interested, I can open-source a version of the type parser with the JS translated into pure Elm. I'm using it in a closed-source project of mine. |
@joonazan no, sorry, I don't know any more. The commit message says. "Superseded by elm-tools/parser and elm-tools/documentation" but I didn't dig any deeper. |
I found that the package.elm-lang.org frontend perfectly solves the problem for which I have used this library. The type parsing code there might be helpful in this project.
https://github.com/elm-lang/package.elm-lang.org/blob/master/src/frontend/Parse/Type.elm
The text was updated successfully, but these errors were encountered: