Bug was found too late, near code freeze for rtm, not enough time for fix. fix is in progress ( https://github.com/Microsoft/visualfsharp/pull/1290 https://git

Bug was found too late, near code freeze for rtm, not enough time for fix. fix is in progress ( https://github.com/Microsoft/visualfsharp/pull/1290 https://github.com/Microsoft/visualfsharp/pull/1290 ) probably tomorrow, it's not a big problem one or two days of delay. Also because that's an sdk issue (preview2) not of .NET Core (rtm) The f# support is in beta, c# was ahead obv, but that's ok i think, it's used as the language for the corefx, etc. vb is not working at all atm. The .NET Core sdk preview1 worked ok ootb, see for example the https://github.com/SuaveIO/Suave-CoreCLR-sample https://github.com/SuaveIO/Suave-CoreCLR-sample working xplat (win/ubuntu/osx/docker). And the preview1 continue to work. What i really like it's how the sdk it's evolving, using modularized components it's possibile to fix/improve/evolve the f# compiler/library, without waiting a new version of sdk. That's really good. In the next sdk or rtm also the `dotnet new` it's going to be updatable, so np about template too