Microlens exports conflict with Lens

[SomeDer]

I needed to install lens as microlens has too few features. However, RIO exports microlens functions which conflict with the lens functions. This means I have to add a hiding line to every RIO import, which is inconvenient. I think the lens functions should be provided by a separate module, to help avoid this.

[akhra]

We could instead provide RIO.LensFree to satisfy this case, as it does seem likely to come up fairly often. I worry about the precedent, though.

A simple local solution would be to define it yourself:

module RIO.LensFree (module RIO) where
import RIO hiding (<lens stuff>)

[hanjoosten]

I ran into this very issue. I wasn't hindered by any knowledge about this, and assumed importing RIO was safe. As it turns out, importing RIO without hiding stuff will likely break a build with using cabal. See AmpersandTarski/Ampersand#1142

[tonicebrian]

Is there a way to hide RIO.Lens completely? I think that 90% of the time I will use advanced features and I don't want to hide specific functions but RIO.Lens altogether.

[ncaq]

I am thinking that I could bundle the real lens with it.