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

ImmediateIO and TransactionalIO can cause data races

Multiple soundness issues in Ptr

dces' World type can cause data races

CopyCell lacks bounds on its Send trait allowing for data races

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

Future lacks bounds on Send and Sync.

Singleton lacks bounds on Send and Sync.

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

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.

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

Double free when calling sys_info::disk_info from multiple threads

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

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

Thex allows data races of non-Send types across threads

GenericMutexGuard allows data races of non-Sync types across threads

Some lock_api lock guard objects can cause data races

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

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

MsQueue and SegQueue suffer from double-free