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 jackdied
Recipients benrg, jackdied, loewis, r.david.murray, terry.reedy
Date 2010-06-05.01:31:54
SpamBayes Score 0.040253147
Marked as misclassified No
Message-id <>
if the id() of the left operand is identical to the id() of the first element in the result it would strongly support compiler skulldugerry.

class Crasher(tuple): pass
foo = Crasher()
x = [1]
a = x + foo

if id(b) == id(x):
  raise Exception("It's the C compiler what did it!")

The only way I can think of this coming about is the right_op getting new'd and then .extend'ing(left_op).  That extend() must be going batsh*t and inserting the left_op instead of it's contained items.  The C-code for extend is more fiddly than the code for concatenation so there is more room for the compiler to generate bad code.
Date User Action Args
2010-06-05 01:31:57jackdiedsetrecipients: + jackdied, loewis, terry.reedy, r.david.murray, benrg
2010-06-05 01:31:57jackdiedsetmessageid: <>
2010-06-05 01:31:55jackdiedlinkissue8847 messages
2010-06-05 01:31:54jackdiedcreate