Practice
Learn
← Quit
0 / 0 correct
Rust
Hard
1 of 40
Why can a std::sync::RwLock be a poor choice for a read-mostly hot path?
A
RwLock doesn't allow concurrent readers
B
Readers still contend on the lock's internal counter (cache-line bouncing), and writers may starve or block readers depending on the OS
C
RwLock is unsafe
D
RwLock can't hold Vec