-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Generate Apply instances with explicit kind arguments
After the changes in [GHC#23515](https://gitlab.haskell.org/ghc/ghc/-/issues/23515) are implemented, some `Apply` instances will fail to compile due to their left-hand sides being kind-generalized to something that is more polymorphic than what their right-hand sides will allow. For example, this commonly occurs when generating `Apply` instances for lambda-lifted definitions or declarations whose kinds use visible dependent quantification. We avoid this issue by now generating `Apply` instances with explicit kind arguments (via `TypeApplications`), leveraging the fact that we know what the kinds are (most of the time) during defunctionalization. See the new section of `Note [Defunctionalization game plan], Wrinkle 2: Non-vanilla kinds` for the full details. Resolves the "Defunctionalizing declarations using visible dependent quantification" section of #601.
- Loading branch information
1 parent
7bf41e0
commit 95ce374
Showing
113 changed files
with
839 additions
and
775 deletions.
There are no files selected for viewing
60 changes: 30 additions & 30 deletions
60
singletons-base/tests/compile-and-dump/GradingClient/Database.golden
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
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
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
Oops, something went wrong.