Kevin Ransom (msft)
Kevin Ransom (msft)
Fixes #16105 When doing cross assembly optimisation, the FSharp optimiser incorrectly inlines function calls from a second assembly that contain internal method calls to a third assembly assembly, with internals...
The Ahead of time tests are not correctly propagating the failure. Fixes: https://github.com/dotnet/fsharp/issues/17126
**Notice:** the test leg is green, and yet the test actually failed. ![image](https://github.com/dotnet/fsharp/assets/5175830/5b3d7625-ba94-4a28-971a-99fa7e86af87)
I intend to try to refactor F# core into at least two assemblies. 1. fscorlib --- Core types supporting runtime scenarios 2. FSharp.Core --- Types supporting runtime and compilation scenarios...
ExtraTopLevelOperators is an unusual module, it is a bit of a grab-bag of types from all over FSharp.Core. It makes it harder to figure out how to reorganize FSharp.Core if...
**FSharp Interactive debugging was never good, and it has got much worse.** This is a tracking bug to try to collect the activities that may improve it. - [ ]...
This is incorrect behavior, it should select the version of the Sdk that shipped with the VS being executed. ![image](https://github.com/dotnet/fsharp/assets/5175830/000c9f23-08e8-4717-b639-b140627279fe) Edited: Okay, the current Fsi behaviour is this, if you...
The internal scenario with a 30 assembly limit is no longer an issue. It defaults to on anyway.
In this session there are four sperate submissions, all sent in one go by using Alt+A select all then Debug in Fsi from the context menu. Note that locals and...
Visual Studio currently ships a desktop framework version of the F# compiler and F# interactive application in addition to the coreclr versions shipped with the Dotnet SDK. By default Visual...