Henry Schreiner

(If you know you will never have at least --x arguments, that behavior might be reasonable to configure, though).

I think you pasted something into the title and didn't add a description? Not sure what you mean, that just looks like an in-between compile step.

This was first discussed in #194, was originally targeted for 2.0 (and is the reason the `MakeSingleHeader.py` script was rewritten in 2.0), but I didn't have time to implement it...

Please look at the proposal in #338 and see if it looks like what you were thinking.

Returning the error message is preferred, since CLI11 might be able to run without exceptions enabled one day. That's why that signature is used. I think this is a clear...

`boost::program_options` is not a header-only library - it is pre-compiled. The benefit of not having to pre-compile the library comes at a compile time cost, as with all header only...

Technically, CLI11's current design would allow it to have an optional precompiled mode - I think a (very) few other libraries support a dual usage mode. However, it may become...

To support precompilation, all headers would need to be split into two, a declaration and an implementation, then there would be a way to precompile the implementation files optionally. Personally,...

I wonder if something like this would help: - CLI11 uses `std::function` everywhere. Would have to be re-implemented or permission to use it in a BSD software would be needed,...

I'm planning to move the extra transforms and any other less heavily used optional portions to a separate file, that will close this issue when done.