Antoine Pitrou added the comment: Le vendredi 03 août 2012 à 12:15 +0000, Martin v. Löwis a écrit : > So compared to the traditional type checks: > a) this gives a hard compile error, whereas the existing check would > only produce warnings
Warnings are quite visible already, and we try to silence them. > I think the feature is somewhat desirable; I agree code combining > different types in MIN or MAX is flawed - if it is intentional, asking > for an explicit cast is not asking too much. I don't agree. Trying to battle with C's semantics doesn't seem very productive, especially if it's only done in a single pair of macros. If we think that implicit type conversions are too laxist, we should probably use a different set of compiler options. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15530> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
