Rauhul Varma

@floam if you describe the changes needed in detail, I (if I can find time) or another contributor could implement them.

Couple questions and suggestions: - Did you build with -Osize? - Have you tried running `strip `? (swift binaries contain a ton of symbols data) - Is your binary "fat"?...

> N.B. strip invalidates the signature so even if it is smaller you can't run it. You can either resign the binary with `codesign` or--if you're building with an xcodeproject--use...

I agree that swift-argument-parser does greatly inflate binary sizes and that this is a problem worth addressing. However, step one understanding how much binary executable data the library adds. For...

Running `bloaty` on the example math command has some interesting results: ``` ➜ bloaty math FILE SIZE VM SIZE -------------- -------------- 41.8% 680Ki 40.9% 680Ki String Table 28.1% 456Ki 27.4%...

The issue is most likely because `swift run` is eating the `--verbose` flag

[repro.zip](https://github.com/apple/swift-argument-parser/files/7836704/repro.zip) ``` ➜ repro swift run repro [3/3] Build complete! Verbose Logging Enabled: false ➜ repro swift run repro --verbose /usr/bin/xcrun --sdk macosx --show-sdk-platform-path /usr/bin/xcrun --sdk macosx --find xctest /usr/bin/xcrun...

@erica I don't know if you're still following this issue, but does main (after the #412 merge) solve this issue? Arguments with `visibility: .hidden` will only show up in the...

As a new user to Lifecycle, I found the need to erase my `EventLoopFuture` to `EventLoopFuture` a bit cumbersome/unintuitive. I had to store the result of start in a sideband...

I would consider this a logic bug and be a reasonable cause to `fatalError` or `preconditionFailure`.