> given arrowchoice, i withdraw my proposal. thank you for pointing me there.
Please don't.
While I agree that duplication is undesirable, I urge you all to consider the begginers and even intermediate haskeller point of view.
A search on hoogle will reveal nothing. A search on hayoo will reveal Data.Either.Combinators, but most users are not even aware of hoogle.
They will probably just google either and end up in Data.Either.
In Data.Either there is _absolutely_ no way to reach the Arrow combinators.
And even if the user somewhat finds Arrows, in an unrelated search, he will also not see the Either use case.
I would even argue that the Arrow abstraction is something that is in a totally different level than such a simple type as Either, and most haskellers will only use (arrows) much further ahead, but I agree this is highly arguable.
So:
> It may be worth adding documentation to Arrow about what they mean
Not only to arrows, please: this documentation is needed _on Data.Either_, which is where most users, I believe, would search for such a funcion.
