Carlana
Carlana
There's already a set proposal that is snagged on iteration. This seems related to that. This could be containers/ordered.Set and containers/ordered.Map and have overlapping methods with containers/set.
This makes a lot of sense, but devil's advocate, should we just tell people to do `iterutils.Index(slices.Backwards(s), v)` in a world where iterutils exists? I think the tricky of it...
What does go doc do with one underscore and one non-underscore return?