capnp-rpc

prepare for v0.27.0 release

• Make Disconnector wait until the connection's shutdown() completes.

prepare for capnp-rpc-v0.26.3 release

• Add new_broken_cap() function.

prepare for capnp-rpc-v0.26.2 release

• Fix panic when re-sending a capability that was imported twice.

prepare for capnp-futures and capnp-rpc v0.26.1 releases

• Avoid panic when Return message contains bad question ID.

• Follow v0.26.0 release of other capnp crates.

• Block nonstreaming calls while there are pending streaming calls, to match the capnproto-c++ semantics.

• Follow v0.25.0 release of other capnp crates.

• Follow v0.24.0 release of other capnp crates.

• Update local::Client for new async fn method signatures.
• Add new_client_from_rc().

• Update for new async fn method support.

• Follow v0.21.0 release of other capnp crates.
• Remove deprecated new_promise_client() function.

• Remove redundant information in the reason field of some RPC errors.

• Add new_future_client() and deprecate new_promise_client().

• Fill in unimplemented!() block to handle case when an export promise resolves to another promise.

• Add support for streaming RPC methods.

• Add support for Request::set_pipeline().

• Use the noFinishNeeded field to elide Finish messages when possible.

• Remove some unneeded fields in Answer and Import.
• Use let else to improve readability.
• Use a tighter size_hint estimate for Resolve messages.

• Use size hint in new_outgoing_message(). Should improve performance somewhat.

• Fix bug where RpcSystem::get_disconnector() misbehaved if called before bootstrap().

• Follow v0.19.0 release of other capnp crates.

• Follow v0.18.0 release of other capnp crates.

• Rename WeakCapabilityServerSet to CapabilityServerSet and remove the old implmentation.

• Add WeakCapabilityServerSet, intended to eventually replace CapabilityServerSet.

• Regenerate code, with rpc.capnp from upstream latest release, version 0.10.3.

• Add reconnect API.

• Remove some unimplemented!() panics.
• Lots of style and formatting fixes that should have no effect.

• Add CapabilityServerSet.

• Include LICENSE in published crate.

• Update for SetPointerBuilder no longer having a To type parameter.

• Turn some disconnect panics into error results.

• Remove deprecated ServerHook impl.

• Expand deprecation note for capnp_rpc::Server.

• Add capnp_rpc::new_client() and deprecate capnp_rpc::Server.

• Check in generated rpc_capnp.rs and rpc_twoparty.rs files, to avoid build-time dependency on capnp tool.

• Follow 0.12.0 release of other capnp crates.

• Export Disconnector struct from capnp_rpc (#140).
• Switch to std::future::Future.
• Update minimum required rustc version to 1.39.

• Update to Rust 2018.
• Update minimum required rustc version to 1.35.

• Remove deprecated items.
• Add ImbuedMessageBuilder to provide functionality that was previously automatically provided by capnp::message::Builder.

• Add RpcSystem::get_disconnector() method.
• Migrate away from some deprecated futures-rs functionality.

• Prevent a double-borrow that could happen in rare situations with ForkedPromise.

• Fix a possible deadlock.

• Drop GJ dependency in favor of futures-rs.
• Fix a bug that could in rare cases cause Disembargo messages to fail with a "does not point back to sender" error.

• Eliminate some calls to unwrap(), in favor of saner error handling.
• Eliminate dependency on capnp/c++.capnp.

• Directly include rpc.capnp and rpc-twoparty.capnp to make the build more robust.

• Fix "unimplemented" panic that could happen on certain broken capabilities.

• Fix bug where piplining on a method that returned a null capability could cause a panic.