Author benjamin.peterson
Recipients benjamin.peterson, loewis, vstinner
Date 2012-04-23.23:06:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPZV6o8qFoRAn+vqLvhhGDJupLR4HBQT7P4a8dnyKqPt-uqy8A@mail.gmail.com>
In-reply-to <20120424004507.Horde.BWpocKGZi1VPldtzCRAXVNA@webmail.df.eu>
Content
2012/4/23 Martin v. Löwis <report@bugs.python.org>:
>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
>>> What's the specific warning that you want to eliminate?
>>
>> "control reaches end of non-void function without return"
>>
>> Basically, whenever you see "assert(0)" today.
>
> Sorry, what I meant is: what specific line (in what specific
> source file) is that warning on?
>
> If there is an assert(0) somewhere, there should be no
> subsequent code, so no such warning should be generated.

Right, we currently avoid this problem by writing "assert(0)" for
example in lookdict_split in dictobject.c. What I'm saying is that
instead writing "assert(0)", we could use Py_UNREACHABLE.
History
Date User Action Args
2012-04-23 23:06:33benjamin.petersonsetrecipients: + benjamin.peterson, loewis, vstinner
2012-04-23 23:06:32benjamin.petersonlinkissue14656 messages
2012-04-23 23:06:32benjamin.petersoncreate