Skip to content

Wingman shouldn't suggest destruct actions for things that are already destructed #1711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
isovector opened this issue Apr 11, 2021 · 0 comments · Fixed by #1715
Closed

Wingman shouldn't suggest destruct actions for things that are already destructed #1711

isovector opened this issue Apr 11, 2021 · 0 comments · Fixed by #1715
Labels
component: wingman type: enhancement New feature or request

Comments

@isovector
Copy link
Collaborator

Related to #1704, if we had a consistent hypothesis throughout a definition, Wingman could notice that there is already provenance from a given value. Therefore, it must have already been destructed, and we shouldn't suggest it. That would clean up a lot of the spurious suggestions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: wingman type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't suggest destruct actions for already-destructed terms isovector/haskell-language-server
1 participant
@isovector