Re: Overloaded record fields

24 Jun 2013


      -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/06/13 11:05, Mateusz Kowalczyk wrote:
...
On 24/06/13 11:04, Roman Cheplyaka wrote:
...
* Mateusz Kowalczyk  [2013-06-24 
10:47:09+0100]
...
Restricting function composition to have spaces around it will 
require changing a large amount of existing code if one is 
willing to use it.
...
I assume this semantics will be triggered only by an extension,
so there'd be no need to change existing code.
...
...
While I personally would like the restriction because I hate 
seeing people skimp out on whitespace around operators, there
are a lot of people with a different opinion than mine and I
imagine it'd be a great inconvenience to make them change their
code if they want to start using SORF.
...
Well, if they *want* it, it's not unreasonable to require them
to *pay* for it (in the form of adjusting their coding style).
...
Roman
Sure that it's unreasonable to have them change some of their code
to use new, cool features. I'm just questioning whether it's
absolutely necessary to do it by forcing restrictions on what is
probably the most commonly used operator in the whole language.
_______________________________________________ 
Glasgow-haskell-users mailing list 
Glasgow-haskell-users@haskell.org 
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
That meant to say `that it's *not* unreasonable'.
- -- 
Mateusz K.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBAgAGBQJRyBp0AAoJEM1mucMq2pqXHbEP/3myuTjcUiG59ee3/32PFZTQ
Qb0308VmgTzTMhZCKosn+iymgLm1DFThR5P3aOgRgixn2gnvIpf7tu3GhAYvn+5Q
BzpNwWOt17+sFBf0ovLW3bdFmKDQhzPy5OTtCcTDBAf6AyRJLFlTFRMFl4oQWpuF
KI34M0gNwKjh2NIDk3z21afVG7go9rdxtRZwMV9OqVwFgeAKJ4QY2U5kPu47p8cr
HOZzaPsPsdf89Izaun8X3ApYLO0fDvi55nbogTJCEN+BoqK/+ZE/upDAoLJB4k6m
iuFA86RmfJfHgrIWp2EpR3G7G6+jW/1gwOrx5RjXjyW6SzBTBuhcBQdmtIZXTqih
PhpWMmydS4iwYJWIAekiPbO2pCFlgeN++NJ4fyt2b8ypVfRm27k+xjfRso/up9gf
dNgU7WXlx1tm0mzLWzauMojK65HEDVd8IjQ0DRj9Prmr0EiB9e/KbrR592YFAl+p
7fvAGxV5Vc83LRN0smIg9RrHrPe8hVeDJTKbU5KU0QURil3RIMatIy0MNebIoz6u
csnmcXBKmYKGMifAvNYLOFGrwlvIEGdb0oPDf8WlP2A6LPDEecBLW1x9KUIMeLVf
b/x8KiGVw49J4Osr0vwI3U8ThxgrksNqHVPdxLYS5GvbPT8+74EPmMTVTixFOROY
oK26lPQ7hEUb++bGCBR+
=QZmK
-----END PGP SIGNATURE-----