`&` shadows the same operator in `Data.Function` in `base`

[miniBill]

& is usually reserved for a function of type a -> (a -> b) -> b, but superrecord's & shadows it

Also, because of #17, it's impossible right now (with the hackage version) to just re-export it with a different name.

I understand that changing that name would be a huge breaking change, how about deprecating it and using something else? I'd use &=, but I must admit I haven't surveyed the conventions enough to be confident in my suggestion

[sboosali]

yeah, and I always import (&) from base my custom prelude.

[miniBill]

Indeed my issue stems from a custom Prelude exposing &, in which I'd like to try using superrecord