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.

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

Type variables resolution #2

Open
feuerbach opened this issue Dec 1, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@feuerbach
Copy link
Member

commented Dec 1, 2012

No description provided.

@Lemmih

This comment has been minimized.

Copy link
Member

commented Apr 29, 2014

Why is this low priority?

@feuerbach

This comment has been minimized.

Copy link
Member Author

commented Apr 29, 2014

"Low priority" for me, not for the project. If you or someone else implement this, I'd be happy to merge.

For me it's low priority because:

  • it's not required by any of the things I'm doing with haskell-names
  • it's somewhat tricky to implement (type vars may be implicitly bound, and their scope may escape the subtree where they are bound)
  • it's mostly useful for type checking, but I'm not aware of any ongoing efforts to do typechecking on top of haskell-names/haskell-src-exts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.