胡雨軒 Петр

When the developer know that something is dangerous and would to fully collect the informed consent of the user: - In an interactive shell a prompt asks for confirmation; -...

- Perhaps it should not exit after some time to make sure that the user notice that the program is blocked. - Otherwise, with a countdown it might just appear...

For example one should be able to express that thw two operands should be linked to configuration keys `--source` and `--target`.

Currently the order is env var, default config file, config provider, command line, repl override.

For example `--language` can be repeated several time to specify several language. A property of the schema should reflect this.

- Subcommand are just arguments - Some (sub)command may have different, overlapping requirements - Basically should automate the need for `cond` in `-main`, while enabling simple enhancement or à-la-carte replacement....

Provide default options that may be overriden or just disabled by the dev user - `--help`, `-h`, `-?` - `--now`, `--start-time`, `-t` - `-!`, `--about` - `-v`, `--verbose`, `log-level`, `-d`,...

Defaults: - boolean: 0 - string and probably everything else: 1

- It should be possible to (recursively) hide some options or nested map from the summary. - `:description`, as expected, should be the actual description as per malli convention. However...

So that at least it gives an estimate of how long the parsing process may take. We should also link to mallk own perf test. As this is a tiny...