2 unstable releases

0.1.0-alpha.1 Aug 20, 2020
0.0.0 Apr 22, 2020

Unlicense

22KB
447 lines

async_chanx

standard-readme compliant Build Status Docs crates.io

Impl Sink for common async channel implementations.

This library implements the missing Sink implementation for common async channels like tokio-sync. It introduces a common error type for channel senders and wraps some implementations that already provide Sink, to make it ergonomic to abstract out over them.

This serves 2 purposes:

  • for libraries: let your users decide which channel implementation to use in your library. The main benefit of this is where this will change the behavior of your lib: bounded vs unbounded, backpressure vs overwriting older messages etc.
  • conveniently compare the performance of channel implementations for your workload by making them plug and play.

DEVELOPMENT STATUS: alpha! I decided to push this on crates.io to facilitate progressing on and publishing alpha versions of other crates that use this. It completely lacks polish and is not recommended for production until it reaches 0.1. Testing, examples and documentation are largely missing and algorithms still need to be reviewed.

Currently I'm waiting to see if async-channel will implement Sink, so I don't have to do it here and then I will work on polishing this some more.

Table of Contents

Install

With cargo add: cargo add async_chanx

With cargo yaml:

dependencies:

   async_chanx: ^0.1

With Cargo.toml

[dependencies]

    async_chanx = "0.1"

Upgrade

Please check out the changelog when upgrading.

Dependencies

This crate has few dependencies. Cargo will automatically handle it's dependencies for you.

There are no optional features.

Security

Usage

Basic example


API

API documentation can be found on docs.rs.

Contributing

Please check out the contribution guidelines.

Testing

Code of conduct

Any of the behaviors described in point 4 "Unacceptable Behavior" of the Citizens Code of Conduct are not welcome here and might get you banned. If anyone, including maintainers and moderators of the project, fail to respect these/your limits, you are entitled to call them out.

License

Unlicence

Dependencies