Deprecate (:>>) because GHC can't efficiently handle recursive type families #101
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
arybczak
force-pushed
the
no-recursive-tf
branch
from
71f698e to
10ea91e
Compare
arybczak
changed the title
arybczak
changed the title
…amilies It's really saddening since (:>>) is a great QoL feature, but if people use it in a lot of type signatures in a non-trivial codebase, it'll start taking forever to compile their code and they'll think it's the fault of the library. This was already encountered in the context of effect libraries: joshvera/effects#49 Relevant GHC issue: https://gitlab.haskell.org/ghc/ghc/-/issues/19238
arybczak
force-pushed
the
no-recursive-tf
branch
from
10ea91e to
aa89585
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
It's really saddening since (:>>) is a great QoL feature, but if people use it in a lot of type signatures in a non-trivial codebase, it'll start taking forever to compile their code and they'll think it's the fault of the library.
This was already encountered in the context of effect libraries: joshvera/effects#49
Relevant GHC issue: https://gitlab.haskell.org/ghc/ghc/-/issues/19238