> Did you find any limitations of `pico-args` turned into a caveat for tuc?

Quite the opposite, early on I started with `clap`, then moved briefly to `argh` before settling with `pico-args`. Compilation time and size where the main driving factors, alonside support for non-spaced values (e.g. -d' ').

Maybe if tuc had subcommands it would have been a different story, but I didn't find enough value in more blasoned arg libraries.