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

Increase precedence of parsing variable names #83

Merged
merged 1 commit into from
Feb 7, 2018

Conversation

Gabriella439
Copy link
Contributor

The purpose of this change is to permit identifiers that begin with
reserved keywords. Here are some example issues due to Dhall
previously not supporting that:

After this change, names like List/map or TypeSynonym
would become legal. However, this should not break any
existing code because variable names will still reject reserved
identifiers.

The purpose of this change is to permit identifiers that begin with
reserved keywords.  Here are some example issues due to Dhall
previously not supporting that:

* dhall-lang/dhall-haskell#250
* #59

After this change, names like `List/map` or `TypeSynonym`
would become legal.  However, this should not break any
existing code because variable names will still reject reserved
identifiers.
@Gabriella439 Gabriella439 merged commit de34357 into master Feb 7, 2018
@Gabriella439 Gabriella439 deleted the gabriel/reserved_prefix branch February 7, 2018 06:31
Gabriella439 added a commit to dhall-lang/dhall-haskell that referenced this pull request Feb 7, 2018
... as standardized in dhall-lang/dhall-lang#83

Fixes #250

This allows identifier names to begin with reserved identifiers.  For
example, previously `TypeSynonym` was not a valid identifier because it
began with `Type` and now it is a valid identifier.
Gabriella439 added a commit to dhall-lang/dhall-haskell that referenced this pull request Feb 8, 2018
... as standardized in dhall-lang/dhall-lang#83

Fixes #250

This allows identifier names to begin with reserved identifiers.  For
example, previously `TypeSynonym` was not a valid identifier because it
began with `Type` and now it is a valid identifier.
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

Successfully merging this pull request may close these issues.

None yet

1 participant