Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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,842
    • Issues 4,842
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 454
    • Merge requests 454
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #20771

Closed
Open
Created Dec 02, 2021 by sheaf@sheafMaintainer

Be more specific when reporting import errors

Currently, with code such as:

import Blahblah1 -- does not export foo
import Blahblah2 (foo)

bar = Blahblah1.foo

We simply get an error saying that Blahblah1 does not export foo. But we could do suggest more fine-grained information:

  • suggest that the user might have mis-spelled Blahblah2 (as that module does export foo),
  • perhaps Blahblah1 defines foo but does not export it, so we could suggest that foo be added to the export list of Blahblah1 (perhaps only if Blahblah1 is from the current package).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking