orphan-crippler 0.1.6

Two-way oneshot channel for task abstraction
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

# Deprecated


[`crossbeam_channel`](https://crates.io/crates/crossbeam-channel) and [`async_channel`](https://crates.io/crates/async-channel) have more efficient and more well-tested single-item channels than this crate does. From this point on, this crate is deprecated.

# orphan-crippler


[![Build Status](https://dev.azure.com/jtnunley01/gui-tools/_apis/build/status/notgull.orphan-crippler?branchName=master)](https://dev.azure.com/jtnunley01/gui-tools/_build/latest?definitionId=14&branchName=master) [![crates.io](https://img.shields.io/crates/v/orphan-crippler)](https://crates.io/crates/orphan-crippler) [![Docs](https://docs.rs/orphan-crippler/badge.svg)](https://docs.rs/orphan-crippler)

The `orphan-crippler` crate is designed to assist in building abstractions where work is offloaded to another
thread, for reasons such as blocking or OS-specific threads. For this reason, `orphan-crippler` implements the
Two-Way Oneshot (`two`) channel type, that allows one to send data to another thread and get more data in
response.

## Features


The optional `parking_lot` feature replaces the usual `std::sync::Mutex` usage in this crate with those from
the `parking_lot` crate. This pulls in a handful of other dependencies and is only really recommended if you are
already using `parking_lot` elsewhere in your application.

## License


MIT/Apache2 License