Skip to content

Type checker version 3 #1

Description

@ENvironmentSet

Current type checker has (at least) three big problems.

  • Insufficient type error message (lack of information of code line where type check fails, constraints of unification variable do not provide information about what they are, how to fix them when they fail)
  • Mutations (TypeMap and LCUVar are mutable object)
  • high coupling of normal type check logic and back propagation logic of unification variable.

To go further, we need to rewrite type checker once again. I'm looking for ideas, hope you share your idea here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    designThis Issue is related to software designhelp wantedExtra attention is needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions