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

ImmediateIO and TransactionalIO can cause data races

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

Multiple soundness issues in Ptr

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

dces' World type can cause data races

Future lacks bounds on Send and Sync.

Thex allows data races of non-Send types across threads

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

Singleton lacks bounds on Send and Sync.

Generators can cause data races if non-Send types are used in their generator functions

CopyCell lacks bounds on its Send trait allowing for data races

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

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

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

Some lock_api lock guard objects can cause data races

GenericMutexGuard allows data races of non-Sync types across threads

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

Double free when calling sys_info::disk_info from multiple threads

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

MsQueue and SegQueue suffer from double-free