Message159805
| Author |
loewis |
| Recipients |
benjamin.peterson, ezio.melotti, georg.brandl, loewis, pitrou, vstinner |
| Date |
2012年05月02日.15:54:04 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1335974045.28.0.671054253737.issue14656@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I was just attempting to provide a standard way of marking unreachable code.
I'm -1 for the proposed patch (and probably -0 on the general idea). I think the patch has the potential *introducing* new warnings, as compilers might warn that a return is lacking in these functions.
I'm -0 on the general idea, as I think the status quo is just fine.
As for Victor's second use case (run-time checking that supposedly-unreachable code is indeed not reached, in release mode), I'm -0 also: we check that in debug mode; this looks sufficient to me. |
|