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,868
    • Issues 4,868
    • 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
  • #17525
Closed
Open
Created Nov 27, 2019 by Ben Gamari@bgamari🐢Maintainer

Backpack documentation is lacking

Since its merge Backpack has been long lacking in the documentation department. In particular, there are several questions of the implementation that are currently unaddressed in the codebase:

  • What is the motivation for and semantics of the .bkp file format?
  • How do Cabal (and other build systems) interact with
  • Where are the Notes that do discuss Backpack found?
  • How does Backpack interact with the EPS? How are hole instantiations incorporated into UnitIds?
  • What shortcomings does the current implementation suffer from? For instance, until very recently (#17188 (closed)) -j was not supported under Backpack. There are also known limitations regarding promotion (#13149). Do we have a comprehensive list of such limitations somewhere (perhaps in the user documentation)?

Furthermore, the users guide has not a single mention of the feature, its motivation, or user-facing interface.

Edited Nov 27, 2019 by Ben Gamari
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking