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 :-)