Proposal: Remove HFunctor's fmap' with GHCs supporting QuantifiedConstraints. #153
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.
As was mentioned in the
HFunctor
documentation, we can eliminate thevestigial
fmap'
method with QuantifiedConstraints. This implementationis provided by Bottu et al.'s Quantified Class Constraints.
The advantage of this patch is that it expresses the nature of
HFunctor
in a more direct manner, rather than with thedummy-function workaround. The disadvantage is that only GHC 8.6
supports QuantifiedConstraints, so we have to use CPP to define the
polyfill (as it were) to handle it.
This changes the
HFunctor
interface but should maintaincompatibility, as
fmap'
was never implemented by hand outside ofSum
.