Data race when sending and receiving after closing a oneshot channel

AtomicBucket unconditionally implements Send/Sync

Intern: Data race allowed on T

Queues allow non-Send types to be sent to other threads, allowing data races

conquer-once's OnceCell lacks Send bound for its Sync trait.

Demuxer can carry non-Send types across thread boundaries

Soundness issue: Input can be misused to create data race to an object

Queues allow non-Send types to be sent to other threads, allowing data races

ShmWriter allows sending non-Send type across threads

SyncRef's clone() and debug() allow data races

UsbContext trait did not require implementers to be Send and Sync.

ButtplugFutureStateShared allows data race to (!Send|!Sync) objects

RingBuffer can create multiple mutable references and cause data races

MvccRwLock allows data races & aliasing violations

Aovec lacks bound on its Send and Sync traits allowing data races

Soundness issue with base::Error

dces' World type can cause data races

Future lacks bounds on Send and Sync.

ImageChunkMut needs bounds on its Send and Sync traits

Thex allows data races of non-Send types across threads

ArcGuard's Send and Sync should have bounds on RC

Unsound: can make ARefss contain a !Send, !Sync object.

MPMCConsumer/Producer allows sending non-Send type across threads

convec::ConVec unconditionally implements Send/Sync

QueueSender/QueueReceiver: Send/Sync impls need T: Send

Cache: Send/Sync impls needs trait bounds on K

Slock allows sending non-Send types across thread boundaries

ReadTicket and WriteTicket should only be sendable when T is Send

TryMutex allows sending non-Send type across threads

Singleton lacks bounds on Send and Sync.

CopyCell lacks bounds on its Send trait allowing for data races

SyncChannel can move 'T: !Send' to other threads

PinSlab and Unordered<T, S> need bounds on their Send/Sync traits

Data race and memory safety issue in Index

Queue should have a Send bound on its Send/Sync traits

Send/Sync bound needed on T for Send/Sync impl of RcuCell

LockWeak<T> allows to create data race to T.

Send/Sync bound needed on V in impl Send/Sync for ARCache<K, V>

Bunch unconditionally implements Send/Sync

Shared can cause a data race

AtomicBox lacks bound on its Send and Sync traits allowing data races

ReaderResult should be bounded by Sync

hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.

may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.

AtomicBox implements Send/Sync for any T: Sized

LateStatic has incorrect Sync bound

Decoder<R> can carry R: !Send to other threads

TreeFocus lacks bounds on its Send and Sync traits

Some lock_api lock guard objects can cause data races

GenericMutexGuard allows data races of non-Sync types across threads

AtomicOption should have Send + Sync bound on its type argument.

beef::Cow lacks a Sync bound on its Send trait allowing for data races

MutexGuard::map can cause a data race in safe code

Unsafe Send implementation in Atom allows data races

Multiple security issues including data race, buffer overflow, and uninitialized memory drop

Improper Sync implementation on FuturesUnordered in futures-utils can cause data corruption

Insufficient synchronization in Arc::get_mut

MutexGuard<Cell<i32>> must not be Sync