fix!: non-helpful max inlines error messages #5
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
Refactor derivation of Arbitrary-instances so that it is (much) more likely that in case of "Maximal number of successive inlines exceeded", the compiler error message will be the expected one. This change is somewhat breaking as it increases the inlining steps for products by one, so it slightly reduces the threshold for hitting that limit. (This could have been avoided at the price of writing redundant code, but that didn't seem worth it.)
MartinHH
commented
Apr 22, 2023
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.
Refactor derivation of Arbitrary-instances so that it is (much) more likely that in case of "Maximal number of successive inlines exceeded", the compiler error message will be the expected one.
This change is somewhat breaking as it increases the inlining steps for products by one, so it slightly reduces the threshold for hitting that limit. (This could have been avoided at the price of writing redundant code, but that didn't seem worth it.)