Tactic plugin: Excludes Dictionary arguments in GADTs in Destruct Tactic #474
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.
Consider the following:
If we select
case split on gadt
at_decons
, the Tactic Plugin in HEAD introduces instance dictionary in data constructor:As it stands, generated pattern includes dictionary argumetns, which must not (cannot) appear in the source language.
This behaviour is due to the call to the
dataConInstArgTys
, which also includes dictionary argument.This pull-request changes to use
dataConInstOrigArgTys
, which excludes dictionaries and adds a golden test for destructing GADTs, and the above case-splitting generates the expected result:One concern: I also change the use of
dataConInstArgTys
inbuildDataCon
todataConInstOrigArgTys
. This should also correct the expression constructed by Homo or Auto tactic, but the generated expressions don't take type-level constraints into account. Any thoughts?