Message323468
IMHO we shouldn't expose the intern dictionary without there being a clear, and good enough, use case for doing so.
Exposing the dictionary decreases implementation flexibility, and increases requirements on other implementations. One example of the former: at least in theory the interning dictionary could be a set, but we couldn't make that change if the dictionary were exposed in the API.
With current information I'm -1 on exposing the dictionary, and -0 on doing that for debug builds only. |
|
Date |
User |
Action |
Args |
2018-08-13 08:23:44 | ronaldoussoren | set | recipients:
+ ronaldoussoren, rhettinger, rushter |
2018-08-13 08:23:44 | ronaldoussoren | set | messageid: <1534148624.65.0.56676864532.issue34386@psf.upfronthosting.co.za> |
2018-08-13 08:23:44 | ronaldoussoren | link | issue34386 messages |
2018-08-13 08:23:44 | ronaldoussoren | create | |
|