Le Tue, 8 Oct 2013 08:21:43 +0200, Antoine Pitrou <solipsis at pitrou.net> a écrit : > > > I think there *is* a potentially worthwhile generalisation here, > > but I'm far from sure "is-a-dict" is the right data model - for > > composability reasons, it feels like a "has-a" relationship with an > > underlying data store may make more sense. > > It doesn't work. Your "underlying mapping" can show too much variation > for the wrapper/proxy to have sane semantics. For example, how do you > combine with a defaultdict or a WeakKeyDictionary, knowing that the > wrapper/proxy has to have its own internal mapping as well? (for the record, I'm saying that because I did try the composition route.) Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4