4 ms·
The hard part of removing GIL are the language semantics themselves. Replacing CPython's reference counting with some kind of tracing GC will still leave you wi
by dfox 9y ago
The hard part of removing GIL are the language semantics themselves. Replacing CPython's reference counting with some kind of tracing GC will still leave you with problem of coming up with low-overhead thread-safe dictionary implementation.
- hyperpape 9y agoI agree with the first sentence. For the second part, what are you thinking of? For reads, there's very low overhead for using an implementation like Java's ConcurrentHashMap. The overhead for insertions is more significant, but not enormous.