-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add named versions of the standard F#x operators #52
Comments
I agree. I wonder if this couldn't be done in conjunction with finishing the pull request for type classes? We really should finish that one out. |
@panesofglass It's nagging me too, but I think they're independent issues... |
I almost never use symbolics as I like to have the option of intellisense. When you come back to code you have written previously its really annoying to not be able to see the function signature of the symbolics. Or having to alias the symbolic back to a named function so you can. |
@7sharp9 Do you agree with the tentative names I proposed? Are there any other operators I didn't include? |
@mausch I think so, they seen sensible to me. |
@mausch I know they wont be as pretty as infix symbolics, its a pity we don't have infix function declarations. |
@mausch theres also (>>.) If you include the ones in the Nullable module: (+?), (-?), ( *?), (/?), (>?), (>=?), (<?), (<=?) |
@7sharp9 About the Nullable module, since F# 3.0 already has operators around Nullable and they're much better than the ones in this module, these operators are pretty much deprecated. I'll remove them when we upgrade to FSharp.Core 4.3 / 2.3 |
Revisiting this issue, I'm having second thoughts about those names... here are some other suggestions:
So yeah, bikeshedding :) |
👍 for |
We have a lot of cool operators in F#x. Let's try to give them names and add the named vbersions to the prelude (or the monads).
Pull request are welcome on this issue.
The text was updated successfully, but these errors were encountered: