ghc-lib-parser 9.14 #1175
Draft
ghc-lib-parser 9.14 #1175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amesgen
force-pushed
the
amesgen/ghc-9.14
branch
from
c7dde00 to
ecca531
Compare
The parser started supporting this in 9.14, so let's make sure we format it nicely.
amesgen
force-pushed
the
amesgen/ghc-9.14
branch
from
ecca531 to
0c6b458
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft until GHC 9.14.1 gets released
Update flake inputs and GHCs, bump
.cabalversion boundsAlso drop GHC 9.8 (which allows us to upgrade to GHC2024 in a follow-up PR).
Update to
ghc-lib-parser-9.14. See the changelog entry for new syntactic features.Update to
Cabal-syntax-3.14.Fix Strings containing
\^\escape sequence are misformatted #1165 (depends on an upstream GHC parser fix).