diff options
| author | Sebastian Graf <sgraf1337@gmail.com> | 2019-09-27 11:22:33 +0000 |
|---|---|---|
| committer | Marge Bot <ben+marge-bot@smart-cactus.org> | 2019-10-08 13:27:49 -0400 |
| commit | f691f0c21dcc576e02313123e8b091e241d23b51 (patch) | |
| tree | 7e0711dea642c407ef9884b788efec9ed28e28b5 /bindisttest/checkBinaries.sh | |
| parent | c2d4011c403d6746968df8be0633d0a9ac475d09 (diff) | |
| download | haskell-f691f0c21dcc576e02313123e8b091e241d23b51.tar.gz | |
PmCheck: Look up parent data family TyCon when populating `PossibleMatches`
The vanilla COMPLETE set is attached to the representation TyCon of a
data family instance, whereas the user-defined COMPLETE sets are
attached to the parent data family TyCon itself.
Previously, we weren't trying particularly hard to get back to the
representation TyCon to the parent data family TyCon, resulting in bugs
like #17207. Now we should do much better.
Fixes the original issue in #17207, but I found another related bug that
isn't so easy to fix.
Diffstat (limited to 'bindisttest/checkBinaries.sh')
0 files changed, 0 insertions, 0 deletions