Nate Cook

Thanks for this writeup, @bdrelling! I definitely agree that we want to include allowed values in the help text, but I think the right place to handle their definition is...

Those both feel more like edge cases than would justify increasing the API surface at the declaration site. For the first case, you can add any extra information about what's...

Note that this ends up overlapping quite a bit with #8 if we go the `ExpressibleByArgument` route.

@wendyliga Thanks for the feedback! We’ve had a few requests for being able to automatically populate an argument with stdin, so I think it’s worth looking at more. I’m going...

The reason we swallow the error there is that we let you define command structures like this: ```swift struct Root: ParsableCommand { static let configuration = CommandConfiguration(subcommands: [Sub.self]) @Option() var...

@klaaspieter It looks like #10 resolved this — did you have more to do? See 4d57c8c43ff5107e634a55b85bf53c674d06d24c

Ah yes, that's a tricky case! Since it doesn't find `--knd` in the argument set it doesn't know whether it's a flag or an option, so it can't skip over...

Agreed on this, but I think I might want to have three slots available, so it ends up matching the way `man` pages are often layed out: ``` $ example...

Name for this extra configuration property can be `extendedDiscussion`.

That would be great, thanks @arthurcro!