Tomas Grosup
Tomas Grosup
A safe but not all-scenarios-covering change would be: - If source is nullable - Target can be enhanced to be nullable - Insist on the downcasting target to be decorated...
Fixed by https://github.com/dotnet/fsharp/pull/17965
@roboz0r : We have dicussed this addition and have an idea on how to bring the same functionality with a new compiler intrinsic, instead of adding many new functions to...
(coverting to draft due to the suggestions above)
Converted to draft until green, please mark as ready to review once this is ready to be merged.
(Hint: For method calls, this would be coming from `CanMemberSigsMatchUpToCheck` in the `subsumeTypes` invocation. From there the info needs to go to ConstraintSolver to be known at warning time.
@abonie : Is this still relevant?
Will need to change how nullness info is inside TcGlobals (if it should support switching on/off)
Another solution: Support enabling/disabling nullness warning for blocks of code, the nullness feature would be always on.
Resonable default: Enable nullness by default **in the IDE,** but ignore the warnings (FSI adding some default warnings to be ignored) when running the script. #warnon would put them back...