Message8612

@zyasoft, I see your point, too. Were we writing this from scratch, I'd probably use Java's already concurrent collections data structures, too (ConcurrentLinkedDeque, especially, is quite elegant with its non-blocking no-lock mechanisms).

But the "thread-safety" doc on `deque` on CPython doc is also a bit misleading, IMHO. It's "thread-safe" in the same sense that `list` is thread-safe, namely its methods are all implemented in C with the GIL guaranteeing its atomicity per function call. If we want to take this "thread-safety" guarantee the correct way for deque, we'd want to do the same for all the built-in collections data structures like list, set, etc.