Discussion: Expose Haskell-LSP-types and Haskell-LSP from the same package
- Dominant language
- Haskell
- Stars
- 423
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
In cabal 3 it is now possible for a package to have multiple public libraries. https://fgaz.me/posts/2019-11-14-cabal-multiple-libraries/
This would fix the issue where we have two packages in deadlock (Haskell-LSP-types and Haskell-LSP must be the same version) whilst also allowing us to split them out.
On the other hand it is a breaking change, requiring at least cabal 3.0 and GHC 8.8. There seems to be some caveat with cabal-install too. We should possibly look at doing this later once support for it becomes more widespread
Contributor guide
Research direction
Start by reviewing the linked Cabal multiple-libraries proposal and the current separation between Haskell-LSP-types and Haskell-LSP. Investigate the stated Cabal, GHC, and cabal-install compatibility caveats; done means deciding whether a single package can expose both libraries without unsupported toolchain requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100