Tomas Grosup
Tomas Grosup
- Overriding .ToString on an F# type will warn if it returns nullable string - Calling .ToString on F# types with generated ToString (powered by sprintfn %A under the hood)...
When an older compiler encounters a .dll built with a newer one, it can happen that newly added language constructs (not understood by the old compiler) are represented in binary-pickle-format...
Implements https://github.com/dotnet/fsharp/issues/16800 Follows https://github.com/dotnet/runtime/blob/main/docs/design/features/byreflike-generics.md Builds upon: https://github.com/fsharp/fslang-design/blob/main/FSharp-4.5/FS-1053-span.md Deserves a (small) RFC update: https://github.com/fsharp/fslang-design/pull/787
### Issue description As of now, nullness related errors are coming from comparing pairs of types in the constraint solver, and all the nullness warnings come from here. Which means...
### Issue description Since .fsx files do not have project options, it is not possible to pass in `/checknulls+` except for passing command line switches directly. Make it possible (`#nullness-checking`...
### Issue description Parser recovery rule for a mistake of writing ` null | type` instead of `type | null`. Examples: ```let notAValue: null | string = "hi"``` > test.fs(1,21):...
### Issue description Nullable reference type checking is controlled via project settings in .fsproj file. This suggestion is to create an alternative control mechanism via project property pages setting in...
Click “Files changed” → “⋯” → “View file” for the rendered RFC.
This fixes https://github.com/dotnet/fsharp/issues/17742 . F#-originating code has always been against implicit nulls. Even when null literal was passed into the string function, the null was still replaced with an empty...
### Issue description Methods like: DateTime.Parse Int32.Parse require a non-nullable string. Yet, they do not a report a nullable warning when a possibly null string is passed in. They do...