-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathREADME
More file actions
23 lines (22 loc) · 1.14 KB
/
README
File metadata and controls
23 lines (22 loc) · 1.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
PolyOpt allows a no-repetition specification of program options and then
automatically makes those options work simultaneously as command line options
and as config file options.
- todo: make more general
- support non-DEFAULT config sections in some way?
(right now don't even error if these exist, and they are ignored..)
- support subcommand options nicely? (e.g. git clone .. vs git pull ..)
- don't assume so much in the config processing in general?
- allow changing of names of things that are autogenerated?
- is it awkward that for optArgs, config can only do Nothing vs
Just (Just "lol"), whereas only by command-line option can you get
Just Nothing?
- might add another class of type-inferred functions for case where defArg
is Typeable.. reqArgInf or some such?
reqArgGen ["username"] "u" "USERNAME" [t|String|] [|""|] ==
reqArgInf ["username"] "u" "USERNAME" ""
and
optArgGen ["list-recent"] "l" "N" [t|Int|] [|0|] ==
optArgInf ["list-recent"] "l" "N" (0 :: Int)
unsure. i do think fully general *Gen case should exist for e.g.
argDef being a non-TH-Lift-able type like a function type,
so maybe *Inf is bloat..