Successor-ML VS VisualFSharp

Successor ML

SuccessorML[1], 1ML[2], etc. are pretty close to this in spirit. I've been trying to keep up with the publications around the future of ML, but academic research moves kinda slowly. I'm hopeful we'll see a new definition of Standard ML this decade. I'd tend to agree SML is a great choice -- SML-1997 is still ahead of many languages that came well after it in both features and usability.

[1] https://github.com/SMLFamily/Successor-ML

[2] https://people.mpi-sws.org/~rossberg/1ml/

There's docs about how the compiler generally does optimizations here: https://github.com/dotnet/fsharp/blob/main/docs/optimizations.md

You should add your +1 to https://github.com/dotnet/fsharp/issues/8764, which would add a syntax like #r: project ... to FSI.

So when people are mad about MS and F#, one can see here that: https://github.com/dotnet/fsharp/graphs/contributors MS does a lot more for F# then people being all pessimistic in reddit.

F# AOT feature tracking

Can't speak to the others, but I'm pretty sure the F# team just doubled or tripled in size (it's still small though). Also the GitHub repo is very active: https://github.com/dotnet/fsharp .

Have you tried the workaround listed here? https://github.com/dotnet/fsharp/issues/12239