-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExtCore v1.0 #47
Comments
What is |
I'm interested in ExtCore targeting .NETStandard2.0 |
This could probably do with a new version for NET5 or the version below that... |
Because this lib is long dormant Im having to borrow the code, :-( |
@7sharp9 fork it! |
Easier to borrow a bit, having a nuget would be nice now that dotnet has stabilised a bit. |
@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. |
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 ofFSharp.Core
.Current list of breaking changes that'll need to be made:
TaskBuilder
type, which was never properly implemented.==
operator from Pervasives.fs.Result
active pattern from Pervasives.fs -- it conflicts with the newResult<_,_>
type in FSharp.Core.typehandleof<'T>
) in Pervasives.fs which use inline IL and therefore requirefsc-proto
to build ExtCore.Choice<_,_>
andResult<_,_>
The text was updated successfully, but these errors were encountered: