<br><br><div><span class="gmail_quote">On 7/17/06, <b class="gmail_sendername">Guido van Rossum</b> <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hm. Your objections seem to be purely from a performance tuning POV. I<br>think that if we agree that API-wise this is an improvement (fewer<br>things to learn, set literals problem solved, and dicts grow some<br>useful new methods) we should make a decision to do it and damn the
<br>tuning (I trust Raymond will find a way :-).</blockquote><div><br>+1<br><br>Raymond always finds a way. <br><br>- C<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
--Guido<br><br>On 7/17/06, Michael Chermside <<a href="mailto:mcherm@mcherm.com">mcherm@mcherm.com</a>> wrote:<br>> Guido writes:<br>> > I've also sometimes thought of unifying dicts and sets by implementing
<br>> > set operations on the keys of dicts only.<br>> [... much discussion ...]<br>> > I'm still very much undecided but I don't want to rule this out for<br>> > py3k. Perhaps I'll write up a PEP and see how it flies.
<br>><br>> Playing with it, and PEPing it both sound fine, but I think DOING it<br>> seems like a bad idea.<br>><br>> I see two advantages. One is public: it solves the issue of a set<br>> literal. The other is private: it allows us to reuse the implementation.
<br>><br>> Fixing the set literal just isn't sufficient justification, IMHO. And<br>> as for the implementation, we care VERY much about perfectly tuning<br>> the performance of the dict type, because its performance is so key to
<br>> the implementation of namespaces throughout Python. So I would not want<br>> to accept any unnecessary restrictions on the implementation that might<br>> constrain future optimizations of dict performance.<br>
><br>> Besides, how difficult is it to maintain the existing C implementation<br>> of set and frozenset (now that they're written and have been through<br>> the wringer of being in a production release). It's not zero cost, but
<br>> it's also probably not THAT big.<br>><br>> Of course, that's the idea behind trying it out and even writing a PEP<br>> -- then we'll see whether my guess (or yours!) is correct.<br>><br>> -- Michael Chermside
<br>><br><br><br>--<br>--Guido van Rossum (home page: <a href="http://www.python.org/~guido/">http://www.python.org/~guido/</a>)<br>_______________________________________________<br>Python-3000 mailing list<br><a href="mailto:Python-3000@python.org">
Python-3000@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/python-3000">http://mail.python.org/mailman/listinfo/python-3000</a><br>Unsubscribe: <a href="http://mail.python.org/mailman/options/python-3000/monpublic%40gmail.com">
http://mail.python.org/mailman/options/python-3000/monpublic%40gmail.com</a><br></blockquote></div><br><br clear="all"><br>-- <br>C