Message197533
| Author |
pitrou |
| Recipients |
Arfrever, barry, eli.bendersky, eric.araujo, eric.smith, ethan.furman, mrabarnett, pitrou, r.david.murray, rhettinger, sbt, serhiy.storchaka, theller, tim.peters, vstinner |
| Date |
2013年09月12日.15:12:56 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<2070353657.57060183.1378998771110.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to |
<1378998159.21.0.983330087002.issue18986@psf.upfronthosting.co.za> |
| Content |
> R. David Murray added the comment:
>
> You are conceptualizing this very differently. In our view, this
> data structure is for cases where the original key is the most
> important piece of information (about the keys). The transformation
> in the lookup process is entirely in the service of looking up the
> value paired with that original key when there is more than one
> possible representation of that key. It is the original key that is
> critical when re-serializing the data or otherwise making use of the
> keys for anything other than lookup. So this is about making the
> data structure succinctly model the problem domain, which is what OO
> is supposed to be good at :)
Thanks for putting it much more convincingly than my python-dev
response :-) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年09月12日 15:12:57 | pitrou | set | recipients:
+ pitrou, tim.peters, barry, theller, rhettinger, vstinner, eric.smith, eric.araujo, mrabarnett, Arfrever, r.david.murray, eli.bendersky, ethan.furman, sbt, serhiy.storchaka |
| 2013年09月12日 15:12:57 | pitrou | link | issue18986 messages |
| 2013年09月12日 15:12:56 | pitrou | create |
|