Why we have ProjectConfig and LegacyProjectConfig
Open
cabal-install: v2-build system
type: refactor
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
What's their relation. Legacy sounds like something we should remove eventually, don't we?
ping @dcoutts
Contributor guide
Research direction
Start by locating the definitions and usages of ProjectConfig and LegacyProjectConfig in the Cabal codebase. Trace how each is created and consumed, then determine whether their relationship and any removal path can be stated clearly. Done means an agreed explanation and a concrete decision about retaining, merging, or removing the legacy type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100