Serhiy Storchaka added the comment: > I see two main trends: optimize most cases (optimize most operators for int > and float, ex: fastint5_4.patch) versus optimize very few cases to limit > changes and to limit effects on ceval.c (ex: inline-2.patch).
I agree that may be optimizing very few cases is better. We need to collect the statistics of using different operations with different types in long run of tests or benchmarks. If say division is used 100 times less than addition, we shouldn't complicate ceval loop to optimize it. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21955> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
