Ah, so failure is being used here as a shorthand for the (unglamorous) `Result<(), Box<dyn std::error::Error + Send + Sync + 'static>>` We need to be able to be generic over std::io::Error (StructOpt in this case), and Tide's error types. So Box is the way to go (:
-
-
- 1 more reply
New conversation -
-
-
This Tweet is unavailable.
-
If it turns out this is useful, we're definitely considering writing an RFC! The hopes is that the RFC stage will be eased because we'll have empirical evidence to back up our proposals. E.g. user reports, usage examples, etc. :D But that's all in the future still (:
- 2 more replies
-
-
-
Damn. You are killing lately
-
^^ glad you like it!
End of conversation
New conversation -
-
-
oh, it works with `structopt` \o/
-
Yes! Was gonna be non starter for me if it wasn't
- 1 more reply
New conversation -
-
-
Nice! Is this intended to supersede quicli?
-
We've talked about it, and the answer is "kind of". Quicli contains multiple things, but this would likely replace the `main` macro! cc/
@killercup to make sure I'm not getting anything wrong about their crate (: - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.