-
-
Save cartermp/6b91c3561c6a5efca4288dca37c15edc to your computer and use it in GitHub Desktop.
@amieres Thanks!
#r "nuget"
is definitely the one I'm looking forward to.
Without trying to diminish the work done by everyone involved, I'm wondering though are there more significant changes coming in v5.0?
The changes presented here don't feel like justifying the major version bump. It's more like incremental improvements similar to v4.5, 4.6, 4.7, which were very welcome of course (I love the anonymous records).
@anilmujagic Part of the challenge here is that no two developers share the same definition of what constitutes a major version bump. In addition to this, we're making FSharp.Core a .NET Standard 2.0-only component moving forward, and all new project templates in Visual Studio will be .NET SDK-style only (.NET Framework still supported, but no legacy project files). We're also planning on at least two more language features for F# 5. This is quite a lot more change than any of the 4.5/4.6/4.7 versions, hence the major version bump.
Part of the challenge here is that no two developers share the same definition of what constitutes a major version bump.
I was secretly hoping that major version will bring Typeclasses :)
@SLAVONchick we're planning on doing a #I "nuget:source"
directive to specify that sort of stuff. probably by the next preview.
@cartermp Cool! Thanks!
@cartermp Hello! I've read today about tooling improvements in VS 2019 16.9 Update and I was wondering, is it possible now to specify my own source while using #r "nuget: ..."
? Thanks!
Yes, this is documented here: https://docs.microsoft.com/en-us/dotnet/fsharp/tools/fsharp-interactive/#specifying-a-package-source
@cartermp Thank you! That’s great!
There is a typo here:
it probably should say:
These are fantastic improvements!