summaryrefslogtreecommitdiff
path: root/testsuite/tests/th/TH_ExplicitForAllRules.stdout
diff options
context:
space:
mode:
authorRichard Eisenberg <rae@richarde.dev>2020-12-24 15:04:06 -0500
committerMarge Bot <ben+marge-bot@smart-cactus.org>2020-12-25 03:48:37 -0500
commit164887da63eaac4e786921a9d3591d4b796ee39e (patch)
tree1b07e39811e3dd0c587cf5349a0ee06d5d24cbed /testsuite/tests/th/TH_ExplicitForAllRules.stdout
parentadaa6194753f33a705ac57cd8ddb94dc9aff1f54 (diff)
downloadhaskell-164887da63eaac4e786921a9d3591d4b796ee39e.tar.gz
Use mutable update to defer out-of-scope errors
Previously, we let-bound an identifier to use to carry the erroring evidence for an out-of-scope variable. But this failed for levity-polymorphic out-of-scope variables, leading to a panic (#17812). The new plan is to use a mutable update to just write the erroring expression directly where it needs to go. Close #17812. Test case: typecheck/should_compile/T17812
Diffstat (limited to 'testsuite/tests/th/TH_ExplicitForAllRules.stdout')
0 files changed, 0 insertions, 0 deletions