-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Migrate custom HLint rules to a newer dhall spec (latest version: 10.0.0) #148
Comments
chshersh
changed the title
Migrate to newer dhall spec (latest version: 5.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 5.0.0)
Mar 1, 2019
chshersh
changed the title
Migrate custom HLint rules to a newer dhall spec (latest version: 5.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 6.0.0)
Mar 6, 2019
chshersh
changed the title
Migrate custom HLint rules to a newer dhall spec (latest version: 6.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 7.0.0)
Apr 29, 2019
chshersh
changed the title
Migrate custom HLint rules to a newer dhall spec (latest version: 7.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 8.0.0)
Jul 5, 2019
chshersh
changed the title
Migrate custom HLint rules to a newer dhall spec (latest version: 8.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 9.0.0)
Jul 25, 2019
chshersh
changed the title
Migrate custom HLint rules to a newer dhall spec (latest version: 9.0.0)
Migrate custom HLint rules to a newer dhall spec (latest version: 10.0.0)
Sep 6, 2019
chshersh
pushed a commit
that referenced
this issue
Oct 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What can be done:
constructor
keyword (it became redundant)in
inlet ... in
expressionsMore details here:
This is not urgent. Mostly minor refactorings that doesn't change functionality. It is probably a good idea to accumulate more changes and change more at once.
The text was updated successfully, but these errors were encountered: