Skip to content

Type variables resolution #2

Open
@UnkindPartition

Description

@UnkindPartition
Member
No description provided.

Activity

lemmih

lemmih commented on Apr 29, 2014

@lemmih
Member

Why is this low priority?

UnkindPartition

UnkindPartition commented on Apr 29, 2014

@UnkindPartition
MemberAuthor

"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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @UnkindPartition@lemmih

        Issue actions

          Type variables resolution · Issue #2 · haskell-suite/haskell-names