Antoine Pitrou added the comment: Le 25/11/2015 03:23, Raymond Hettinger a écrit : > > I'm wary of making such extensive changes throughout the codebase > for > an optional processor-specific feature of limited benefit and unproven > worth.
This is indeed non-trivial. What I'm willing to known is if it helps detect unknown bugs and vulnerabilities in the code base (for example when running the test suite or sample workloads). The Py_VARIABLE_SIZE macro is trivial to understand, and is actually a useful annotation to the code (a kind of executable documentation). The BOUNDS macros are a bit more interesting, but their semantics look simple if you don't want to think too much about the underlying HW implementation :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25300> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
