Tim

I've filed https://github.com/rust-lang/rust/issues/44817. In the meantime, a workaround appears to be to add to your Cargo.toml `serde = "*"`. Sorry for the inconvenience; hopefully this will be solved soon!

@bkfox that change was made to track changes in recent nightlies. You'll probably need to upgrade your rustc version. There was a minor version bump, so `cargo update` shouldn't have...

Unfortunately I don't know of anyone actively working on pushing macros 2.0 over the finish line. In the meantime, I'll update the readme to mention this problem and its workaround.

Update: I've torn out all custom errors for now and am just using `io::Error` for errors in the framework stack. This is not intended to be super long-term, but I...

Thanks for the suggestion! I'm sympathetic to this point of view, but the problem is that the best default for a context would do things that `context::current()` doesn't do: -...

@drewkett apologies for never responding to your suggestion! I could potentially see value in an opt-in simple client — I wouldn't want it to be generated by default since it's...

Thanks for the report! If I understand correctly, this is a problem with rustc_term? You may want to file against https://github.com/rust-lang/libtest?

I see the benefit of the simple case of returning boxed futures. On the other hand, I really like not baking in assumptions about how people use it. It's nice...

I'd prefer not a feature flag, because it doesn't allow mixing both kinds of services in a single crate. Also, I think feature flags are only supposed to enable new...

I looked into this briefly, and it appears complex. - need to handle where clauses and trait bounds - need to figure out if type params apply to requests or...