Hide fixities where they are ambiguous to silence Idris 2 v0.7.0 compiler warnings. #24
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
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.
All of these fixities were off by 1 as far as precedence so without giving it too much thought I hid the ones coming from
Builtin.I also hide some ambiguous fixities in test source files and those I would say are actually indicative of a needed change to Collie which happens to export the same operator with the same or different fixities from multiple modules. I'm quite sure the desired way to address this is not have the downstream project hide 2 of 3 fixities, but I did that here in this PR nonetheless for now.