Message218473
The data structure you are asking for bears a resemblance to the data structure used by the email package to record message headers. Email uses a list with a dict-like API cobbled together on top. The difference with your suggestion is that email also needs to record the order of the headers, so just having a list-of-values for each key isn't adequate. Any bets on whether or not we eventually run across a use of .ini format where the exact order of the duplicated keys within the whole list of keys matters? :)
With two use cases that could be served by the same data structure in the stdlib, I wonder if it is worth actually building the abstract data type. Probably not, but I thought I'd raise the possibility anyway :) |
|
Date |
User |
Action |
Args |
2014-05-13 16:34:33 | r.david.murray | set | recipients:
+ r.david.murray, lukasz.langa, dveeden |
2014-05-13 16:34:33 | r.david.murray | set | messageid: <1399998873.23.0.999924433204.issue21329@psf.upfronthosting.co.za> |
2014-05-13 16:34:33 | r.david.murray | link | issue21329 messages |
2014-05-13 16:34:32 | r.david.murray | create | |
|