I think we should re write the comment in English because I found that there are some foreigners followed this repo.

And if we write the comments in English, I believe that there are more and more international developers get involved in this.

ZTransducer is an effectful chunk processing function, and thus forms an arrow. We should add the following combinators on it:

• zipping: (ZTransducer[A, B], ZTransducer[A, C]) => ZTransducer[A, (B, C)]
• racing: (ZTransducer[A, B], ZTransducer[A, C]) => ZTransducer[A, Either[B, C]] looks problematic to implement currently
• both: `(ZTransducer[A, C], ZTransducer[B, D]) => ZTr

#101 Shows an unsupported use case of generics in mbassador. The extent to which generics are supported and the current limitations should be clearly documented.

This code:

let map = DashMap::<i32, i32>::new();
map.insert(1, 2);
let a = map.get_mut(&1);
let b = map.get(&1);

will deadlock. The shard containing 1 gets write-locked, nothing else can access it. This is reasonable behavior but I think it should be documented.

Perhaps more surprising is that this code:

let map = DashMap::<i32, i32>::new();

for i in 0..100

It would be nice if someone can extend the readme file with proper conversion.

The README files should have links to the online documentation for the classes that are used in the example code. This will make it easier for users to follow along with what is going on.