Add benchmark via inspection-testing for the existing test suite#42
Merged
int-index merged 3 commits intomonadfix:masterfrom Apr 5, 2026
Merged
Add benchmark via inspection-testing for the existing test suite#42int-index merged 3 commits intomonadfix:masterfrom
inspection-testing for the existing test suite#42int-index merged 3 commits intomonadfix:masterfrom
Conversation
Haddock builds without optimizations, which leads to borked inspection tests on GHC 9.4.8
Contributor
Author
|
There seems to be an issue with |
int-index
reviewed
Apr 5, 2026
Contributor
Is it ok on GHC 9.6+? We can drop support for older compilers. |
Contributor
Author
|
@int-index Yes, all the other workflows pass fine. |
Contributor
|
Thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ensuring/proving there is no runtime overhead.
Remark: had to remove
errorusage fromtest1, otherwise there seemed to be a source location discrepancy betweentest1andtest1_raw.Closes #7