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,869
    • Issues 4,869
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 456
    • Merge requests 456
  • 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
  • #17545
Closed
Open
Created Dec 05, 2019 by Krzysztof Gogolewski@monoidalDeveloper0 of 3 tasks completed0/3 tasks

Coercion variables appearing where they shouldn't

During review of !2268 (closed), we've discovered a few places where a coercion variable can appear where it shouldn't. Those are calls to "OrCoVar" functions in:

  • newLocal in MkId
  • bindIfaceId in TcIface
  • tcPatBndr in TcPat

that happen when running tests T13990 T14285 T15648.

The goal is to fix this, or come up with a convincing reason that a coercion makes sense there.

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