-
Notifications
You must be signed in to change notification settings - Fork 161
Add support for GHC 9.12 #2941
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
Open
martijnbastiaan
wants to merge
13
commits into
master
Choose a base branch
from
add-ghc912
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add support for GHC 9.12 #2941
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f80ac3b
Add GHC 9.12 support to `clash-prelude`
martijnbastiaan 0f48d6e
Add GHC 9.12 support to `clash-lib`
martijnbastiaan f7c428c
Add GHC 9.12 support to `clash-lib-hedgehog`
martijnbastiaan acd8076
Add source for GHC 9.12 executable
martijnbastiaan 2fe3478
Bump bounds of `clash-ghc`
martijnbastiaan f0f31b8
Apply Clash specific modifications to `src-bin-9.12`
martijnbastiaan 9171bd2
Compile `clash-ghc` warning free on GHC 9.12
martijnbastiaan c553407
Add GHC 9.12 support to `clash-cosim`
martijnbastiaan 230633d
Add GHC 9.12 support to `clash-testsuite`
martijnbastiaan 56dd077
Add GHC 9.12 to CI
martijnbastiaan 56c7d33
Use `data` for `Signed`/`Unsigned` on GHC >= 9.12
martijnbastiaan 6bfa864
Add GHC 9.12 to compatibility matrix
martijnbastiaan 6958d7e
Use `data` for `Signed`, `Unsigned`, `Index`, and `BiSignalOut`
martijnbastiaan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I'm concerned, I'd just put "1.8" there, not the minor. The minor version isn't all that important, and so far we've only indicated the major version. I feel it's kinda implied you pick the latest minor unless there's a strong reason not to.
I also feel a check mark for something we haven't actually tested (Windows and macOS) is a bit too optimistic.
I'm inclined to keep stuff we haven't tested crossed out. If you think crossed out is too negative, maybe we need to add a question mark emoji to indicate "might or might not work, why don't you try".