let "cabal configure -fSomeFlag" produce error for undeclared flags
Open
cabal-install: other
old-milestone: ⊥
type: enhancement
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
(Imported from [Trac #947](http://hackage.haskell.org/trac/hackage/ticket/947), reported by Oblosys on 2012-04-27)
Typos in flags can lead to confusing problems, especially with large projects that take a long time to build. A simple check could be quite useful:
~> hconfigure -fNonExistentFlag -fSomeFlag
cabal: undeclared flag 'NonExistentFlag'. Declared flags are:
ExistentFlag, SomeFlag
Contributor guide
Research direction
Start at the cabal configure option handling and trace how -fSomeFlag is matched against declared flags. Confirm that an undeclared flag produces an error listing declared flags while valid flags still configure normally; the payload names no source file or test, so locate the relevant coverage before changing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100