New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should fmap use <§> for consistency with function application: §? #159
Comments
<§>
for consistency with function application: §
?
I wish |
I use <%> in the basis because it was the closest thing to <$> on the keyboard. I wonder what other languages with Applicative Functors do. |
I think I like |
re: the "hard to type" fear, |
Option-5, for me, since I'm using U.S. Extended. :) |
Ah, fair enough. I suppose it may be cumbersome for some language keyboards? |
@pthariensflame Actually what I was getting at was that you have to switch modifier keys and back again: |
But I'm also a big fan of the consistency argument, so really I'm just torn! |
@sharplet You can have your thumb (of either hand) on Option while your pinky finger (also of either hand) is on Shift. This is generally what I do, and it works pretty well (it's also agnostic to your particular keyboard layout, since the MOD keys aren't going to move). |
As an aside: we really should radar for the use of $ in operator identifiers. It's ridiculous that the language designers get to have it all to themselves just because they use it for one feature. Dupe'able at rdar://19528489 |
Thanks, @CodaFi! |
This thread should be moved into typelift/Operadics. I'm going to close it here. If there's any interest reopen it over there. |
In Haskell, I think
<$>
was chosen for fmap, because$
is used for function application. Perhaps this consistency should be brought to Swiftz's fmap.Should fmap use
<§>
for consistency with function application:§
?The text was updated successfully, but these errors were encountered: