Implement Send for chunk types

[RamType0]

#4

[RamType0]

This clippy error is really weird

error: this implementation is unsound, as some fields in Producer<T> are !Send
--> src/lib.rs:291:1
|
291 | unsafe impl<T: Send> Send for Producer {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: -D clippy::non-send-fields-in-send-ty implied by -D warnings
note: the type of field buffer is !Send
--> src/lib.rs:278:5
|
278 | buffer: Arc<RingBuffer>,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
= help: add bounds on type parameter T that satisfy Arc<RingBuffer<T>>: Send
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#non_send_fields_in_send_ty

error: this implementation is unsound, as some fields in Consumer<T> are !Send
--> src/lib.rs:496:1
|
496 | unsafe impl<T: Send> Send for Consumer {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
note: the type of field buffer is !Send
--> src/lib.rs:483:5
|
483 | buffer: Arc<RingBuffer>,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
= help: add bounds on type parameter T that satisfy Arc<RingBuffer<T>>: Send
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#non_send_fields_in_send_ty

error: could not compile rtrb due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Process completed with exit code 101.

rust-lang/rust-clippy#8045

[mgeier]

Yeah, that's strange.
AFAIU, this lint will be disabled in the next point release which comes out within the next few days.

Interestingly, this lint is not triggered by #75.

[mgeier]

Rust 1.58.1 has been released, I've restarted CI and now it passes.

[mgeier]

What about adding a comment regarding safety?

Maybe something like this:

// WriteChunkUninit only exists while a unique reference to the Producer is held.
// It is therefore safe to move it to another thread.

[mgeier]

I've added comments as suggestions, what do you think about them?