On Feb 12 2016, Chris Barker chris.barker-32lpuo7BZBA@public.gmane.org wrote:
On Fri, Feb 12, 2016 at 12:27 PM, Andrew Barnert via Python-ideas < python-ideas-+ZN9ApsXKcEdnm+yROfE0A@public.gmane.org> wrote:
I look forward to it. Next time I need some variation of this, even if it *isn't* the same variation you end up building, the fact that there's a potential de facto standard for what to call the ".inv" or whatever still helps me, right?
yeah, though I'm not sure I like that name... (can't think of a better one right now, though).
Are there use cases where the set of keys and the set of values is overlapping?
In most cases you can probably get away by not offering an "inverse" object at all, just let regular lookup fall back on value lookup.
(No Cc on replies please, I'm reading the list)