This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients loewis, pitrou, vstinner
Date 2012-08-03.12:35:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343997178.3377.4.camel@localhost.localdomain>
In-reply-to <1343996120.86.0.149995813205.issue15530@psf.upfronthosting.co.za>
Content
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.
History
Date User Action Args
2012-08-03 12:35:29pitrousetrecipients: + pitrou, loewis, vstinner
2012-08-03 12:35:28pitroulinkissue15530 messages
2012-08-03 12:35:27pitroucreate