Fix compilation with Cabal 3.12 #64
Merged
Conversation
This file contains 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
It appears that a change in Cabal 3.12 has caused the dummy Lexer.hs file to no longer be shadowed by the one produced from Lexer.x Moreover, it no longer seems necessary, since `cabal repl` successfully loads the project even when Lexer.hs does not exist in the source (only Lexer.x does) The simple solution seems to simply delete this hacky Lexer.hs file from the source.
alt-romes
changed the title
|
It looks like |
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.
It appears that a change in Cabal 3.12 has caused the dummy Lexer.hs file to no longer be shadowed by the one produced from Lexer.x which causes compilation to fail with
cabal-3.12 install fast-tagsMoreover, it no longer seems necessary, since
cabal replsuccessfully loads the project even when Lexer.hs does not exist in the source (only Lexer.x does)The simple solution seems to simply delete this hacky Lexer.hs file from the source.