Vladimir Marangozov wrote: > [Neil] > > Alternatively, we can expose a new object malloc API that is > > documented not to be thread safe and that may not use the system > > malloc() and free(). > > This doesn't repair broken extensions. Under the second suggestion, > all APIs would be malloc/free, and you'll introduce yet another one, > just to find out after some time that people will mix this new API > with the others just as well... No, the new APIs would default to using pymalloc. "Broken" extensions would still work because the old APIs would always use the malloc(). Neil
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4