Laurence Gonsalves
Laurence Gonsalves
See the following papers for reference: - [GLL Parsing](https://pdfs.semanticscholar.org/7199/48c80707891652a18510a5d199ed3fa62e17.pdf), Elizabeth Scott and Adrian Johnstone - [Modelling GLL Parser Implementations](https://dl.acm.org/citation.cfm?id=1964577), Adrian Johnstone and Elizabeth Scott - [Faster, Practical GLL Parsing](http://dinhe.net/~aredridel/.notmine/PDFs/Parsing/IZMAYLOVA,%20Anastasia%20&%20AFROOZEH%20-%20Faster,%20Practical%20GLL%20Parsing.pdf), Ali...
Hierarchical arguments would make it possible to plug together different modules on the command-line. Usage might look something like: ``` kotlin // Arguments for some module, defined just like program...
`ArgParser` methods like `adding`, `flagging`, etc. should only use the public API, but the `PosixNaming` class is internal.
Sub commands (as used by `git` or `p4`, for example) would be nice: myCommand --foo --bar subcommand --baz --quux The arguments after the subcommand should be disjoint from those of...
As suggested by @mikehearn: > It'd be great if you could provide some screenshots showing what a program that uses argparse looks like to the user, both help text and...
The `--help` for GNU `ls` looks like: ``` --color[=WHEN] colorize the output; WHEN can be 'always' (default if omitted), 'auto', or 'never'; more info below ``` You can say: -...
Part of git-checkout's usage looks like this: git checkout [-p|--patch] [] [--] [...] The `` and `` are both positional arguments. One can disambiguate between a `` and a ``...
It would be nice to be able to be able to enable the processing of arguments from files. For example/ something like: myProgram --foo -@bar --quux might read arguments from...
I wish chandler had a way to auto-upload binaries when creating a new releases on GitHub. The behavior could be something like, for each tag that doesn't already have a...