Skip to content

Fix parsing of variables with keyword prefixes #1584

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

Merged
merged 2 commits into from
Dec 3, 2019

Conversation

Gabriella439
Copy link
Collaborator

Fixes #1583

Note that one prefix is not yet supported: missing, since fixing that is
not easy for the current parsing implementation (as far as I can tell).

Fixes #1583

Note that one prefix is not yet supported: `missing`, since fixing that is
not easy for the current parsing implementation (as far as I can tell).
Copy link
Collaborator

@sjakobi sjakobi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! 👍

I think would be good to have a test for this too.

And does dhall-lsp-server require changes to support these variables too? In that case it would be good to keep track of the discrepancy at least.

... as suggested by @sjakobi

I'm not upstreaming this into the standard test suite yet because the
current parser cannot handle `missing`, which would be necessary to
generate the corresponding CBOR
@mergify mergify bot merged commit 7d01d46 into master Dec 3, 2019
@mergify mergify bot deleted the gabriel/leadingKeywords branch December 3, 2019 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Variables names are not allowed to start with keywords
2 participants