Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,867
    • Issues 4,867
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 457
    • Merge requests 457
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #21330
Closed
Open
Created Apr 01, 2022 by sheaf@sheafMaintainer

Add origins to meta-variables

Simon suggests that we should add origins for metavariables (e.g. "alpha arose from the instantiation of the function f"). This could either be a field of the MetaTv constructor of TcTyVarDetails, or we could have different origins for different kinds of type variables. When unifying metavariables, we will need to combine the origins. Simon suggests that, to start off, we can simply pick the most informative origin and discard the other.

In !7812 (closed) I added origins for ConcreteTv type variables, but extending this to other kinds of metavariables could improve error messages.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking