PyNumber_CoerceEx: this took a shortcut (not doing anything) when the
left and right type were of the same type and not classic instances. This shortcut is dangerous for proxy types, because it means that coerce(Proxy(1), Proxy(2.1)) leaves Proxy(1) unchanged rather than turning it into Proxy(1.0). In an ever-so-slight change of semantics, I now only take the shortcut when the left and right types are of the same type and don't have the CHECKTYPES feature. It so happens that classic instances have this flag, so the shortcut is still skipped in this case (i.e. nothing changes for classic instances). Proxies also have this flag set (otherwise implementing numeric operations on proxies would become nightmarish) and this means that the shortcut is also skipped there, as desired. It so happens that int, long and float also have this flag set; that means that e.g. coerce(1, 1) will now invoke int_coerce(). This is fine: int_coerce() can deal with this, and I'm not worried about the performance; int_coerce() is only invoked when the user explicitly calls coerce(), which should be rarer than rare.
This commit is contained in:
parent
d451ec1cdb
commit
517c7d4fd3
|
@ -163,6 +163,10 @@ Build
|
|||
|
||||
C API
|
||||
|
||||
- PyNumber_Coerce() and PyNumber_CoerceEx() now also invoke the type's
|
||||
coercion if both arguments have the same type but this type has the
|
||||
CHECKTYPES flag set. This is to better support proxies.
|
||||
|
||||
- The type of tp_free has been changed from "void (*)(PyObject *)" to
|
||||
"void (*)(void *)".
|
||||
|
||||
|
|
|
@ -1427,7 +1427,10 @@ PyNumber_CoerceEx(PyObject **pv, PyObject **pw)
|
|||
register PyObject *w = *pw;
|
||||
int res;
|
||||
|
||||
if (v->ob_type == w->ob_type && !PyInstance_Check(v)) {
|
||||
/* Shortcut only for old-style types */
|
||||
if (v->ob_type == w->ob_type &&
|
||||
!PyType_HasFeature(v->ob_type, Py_TPFLAGS_CHECKTYPES))
|
||||
{
|
||||
Py_INCREF(v);
|
||||
Py_INCREF(w);
|
||||
return 0;
|
||||
|
|
Loading…
Reference in New Issue