Le 23/10/2012 12:05, Victor Stinner a écrit : >> Such a restructuring should not result in compilers >> no longer being able to optimize code by inlining functions >> in one of the most important basic types we have in Python 3. > > I agree that performances are important. But I'm not convinced than > moving functions has a real impact on performances, not that such > issues cannot be fixed. I agree with Marc-André, there's no point in compiling those files separately. #include'ing them in the master unicodeobject.c file is fine. Regards Antoine.
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