($$) conflicts with conduit :)
On Fri, Apr 18, 2014 at 6:21 AM, Alexander Berntsen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I would like to strongly oppose the theft of the (&) operator from general use. The proposal to put it in Data.Function, such that you need to know you are importing it, is OK, but it should never go into the Prelude. It is unlikely to ever go into Prelude as '&'. The current patch only
On 18/04/14 12:09, Malcolm Wallace wrote: puts it in Data.Function.
I still maintain that '|>' and '<|' are preferable, and could go in prelude regardless of Data.Sequence.
'&' represents conjunction in my head, and furthermore it does not obviously relate to '$'. To remedy my concerns, I think David Menendez's suggested '$$' should be strongly considered. This also remedies your concern of occupying all the one-character namespace, which makes it a stronger candidate for prelude than '&'.
And I do think that we should have a reverse application operator in Prelude. Sitting in Data.Function it is only barely more convenient than defining it yourself. - -- Alexander alexander@plaimi.net https://secure.plaimi.net/~alexander -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlNQ/L0ACgkQRtClrXBQc7VeRAEAsM1m7l/HYd1huc1UaLf/6S/m 2Da8dzFysp6ruQV4aa4BAIyBb/Ekc3Ohn+OIZRdR+FCQ+PQeaR7X+r7SZfFsF58u =yApD -----END PGP SIGNATURE----- _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe