4 ms·
Yup. If you don't have to care about thread safety on API level, e.g. list, problems such as what's going on currently in gilectomy are no longer yours.
by mdomans 10y ago
Yup. If you don't have to care about thread safety on API level, e.g. list, problems such as what's going on currently in gilectomy are no longer yours.
- DasIch 10y agoThe GIL has atomic bytecodes as a side effect and this assumption has become part of the API. There is nothing on the datastructure side that can be done to "fix" this. In any case memory access should be considered a memory management problem just like allocating and freeing memory is. It needs to be solved on the language level to create sufficiently high level user experience. You can only do that if you're willing to do things very differently such as Rusts Ownership/Borrowing approach.