-
Notifications
You must be signed in to change notification settings - Fork 21
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 isNotNull to FSharp.Core #99
Comments
When this was converted, the comments after the decline showed (by Daniel Robinson, 13 Sept 2016):
So: this was declined because F# should not include negations of operators or functions and not make exceptions, but I think it has made it into the Core after all. |
@abelbraaksma Well spotted :) @forki Ideally this should be removed from FSharp.Core , see your commit here: dotnet/fsharp@374bbc8, thanks |
Will do. But keep in mind that FCS AFAIK already "released" this.
Am 08.12.2016 02:12 schrieb "Don Syme" <[email protected]>:
… Reopened #99 <#99>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#99 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNKGGahrglee3IjBweEGMjz1Mq3e7ks5rF1mJgaJpZM4Kboi6>
.
|
FCS doesn't ship a new FSharp.Core. Mono is still shipping FSharp.Core 4.1.0.0 (though maybe it gets rebuilt with this in it) |
@dsyme why are we removing this API? it's certainly not the only new public Api .core.dll. And on an entirely different note ... why does FCS not ship an FSharp.Core.dll? that seems a bit weird to me |
It was never approved during the design process (indeed was explicitly rejected, because we have a rule not to put "NotXYZ" predicates in the core library), it just crept in during some code cleanup.
FCS is a DLL shipped as a nuget package with dependency on the FSharp.Core nuget package >= 4.4.0.0 (previously >= 4.3.1.0) |
Closing as declined - we added |
add isNotNull to FSharp.Core [13419354]
Submitted by Gauthier Segay on 4/13/2016 12:00:00 AM
2 votes on UserVoice prior to migration
Using "not (isNull a)" in conditions forces usage of parens or pipe operator and is not optimal readability compared to "a |> isNotNull" or "isNotNull a"
let inline isNotNull a = not (isNull a)
in absence of this function, people often take the shortcut of "a <> null" which according to lint is not optimal.
Response
** by fslang-admin on 6/13/2016 12:00:00 AM **
Declining per my comment below.
Don Syme
F# Language Evolution
Original UserVoice Submission
Archived Uservoice Comments
The text was updated successfully, but these errors were encountered: