ExtCore v1.0

[jack-pappas]

Once the Maintainability tasks project is completed, I think we ought to release the new versions of ExtCore as v1.0.0. The reason for the version bump is that the library has been (more or less) API-stable for a long time, but we will need to make a few breaking changes at some point to be able to properly support new versions of F# without having conflicts between ExtCore and newer versions of FSharp.Core.

Current list of breaking changes that'll need to be made:

• Unexpected TaskBuilder behaviour #23: Remove the TaskBuilder type, which was never properly implemented.
• ping pong in documentation of == and === #38: Remove the == operator from Pervasives.fs.
• Result type in ExtCore collides with the Result type in FSharp.Core 4.2 #39: Remove the Result active pattern from Pervasives.fs -- it conflicts with the new Result<_,_> type in FSharp.Core.
• Move tagged collections/modules to separate assembly #43: Move tagged collections to a separate assembly
• Remove the few functions (e.g. typehandleof<'T>) in Pervasives.fs which use inline IL and therefore require fsc-proto to build ExtCore.
• Supporting Result and/or Choice #48: Determine whether and how to support both Choice<_,_> and Result<_,_>

[7sharp9]

What is typehandleof<'T> used for?

[theimowski]

I'm interested in ExtCore targeting .NETStandard2.0
If there are any low-hanging fruits among outstanding issues - please let me know, I'll be happy to help

[7sharp9]

This could probably do with a new version for NET5 or the version below that...

[7sharp9]

Because this lib is long dormant Im having to borrow the code, :-(

[jackfoxy]

@7sharp9 fork it!

[7sharp9]

Easier to borrow a bit, having a nuget would be nice now that dotnet has stabilised a bit.

[jack-pappas]

@7sharp9 I fixed up the build process a few months back (which'll make it significantly easier to build, since it uses the F# compiler nuget packages), just never got around to pushing it up to Github and fixing the CI build. I'll do that sometime this weekend so we can get a new build out that's compatible with .NET core.