Tomas Grosup
Tomas Grosup
I am not aware of all the places which are related to it. Would all the places be covered be removing anything that points to "FSharp.NET.Sdk" from the VMR ?...
This is now being reopened with having RFC FS-1060 (Nullable reference types) in mind. Based on the discussion above, the suggestion would be to support 4 different container types: -...
In C#'s elvis operator, flattening is not a concern - `((string?)?)?` would not make any sense, it naturally just keeps a single level of a possibly missing value. The inclusion...
> > > We will likely not special-case it, as discussed before. We already do not in all other cases. > > > > > > Yes, sorry, changed the...
> ...for any types that followed a pattern of intrinsic or augmented... I would also favor a more universal approach, since I have seen codebases with domain specific option-like types....
Thanks @edgarfgp for getting this in. The resulting parser code is more unified and better readable across the similar syntactical constructs 👍 .
I could imagine a simplified version of this for a `condExpression` and `not(condExpression)`, when using the FSharp.Core's `not` function. But if this is the case, a nested match will do...
I have marked this as `probably not` due to feasibility constraints and correctness of the compiler implementation (example: think about floating point operators). Even though there could be a limited...
Related to: https://github.com/dotnet/fsharp/issues/17409