Skip to content
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

a -> HTMLElement and _ -> HTMLElement have different results #395

Open
alextes opened this issue Jul 13, 2019 · 1 comment · May be fixed by #396
Open

a -> HTMLElement and _ -> HTMLElement have different results #395

alextes opened this issue Jul 13, 2019 · 1 comment · May be fixed by #396

Comments

@alextes
Copy link

alextes commented Jul 13, 2019

Going by the help page for Pursuit my best guess for finding functions that return something of type HTMLElement was HTMLElement or a -> HTMLElement. Neither gives any results although _ -> HTMLElement does. It is not clear why.

hdgarrood suggested they should perhaps return the same results. For me being able to find a written suggestion to try _ vs. a could also be enough.

Thanks for this awesome docs service 🙏 !
@klntsky
Copy link
Contributor

klntsky commented Jul 13, 2019

The solution is probably to insert

 go (P.TypeVar _ _) t = pure (typeComplexity t)

below this line.

In my adaptation of this algorithm I considered all three cases:

  • variable substitution
  • variable instantiation
  • type generalization by a type variable

In pursuit, the third case is not considered.

Most likely this issue is a low-hanging fruit.

klntsky added a commit to klntsky/pursuit that referenced this issue Jul 13, 2019
@klntsky
fix purescript#395
f833e88
@klntsky klntsky linked a pull request Jul 13, 2019 that will close this issue
Open
@hdgarrood hdgarrood mentioned this issue Jul 7, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Treat variables in type queries same as type wildcards klntsky/pursuit
2 participants
@alextes @klntsky