-
Notifications
You must be signed in to change notification settings - Fork 144
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
FSharp.Core planning note #232
Comments
When we can see strategical release? Or at least a strategical plan? Can we hope be a most feature-oriented language in .net? @dsyme - you implement type classes at least two years ago. We must wait when C# realize it? |
@ijsgaus while I sympathize to your suggestion about more open "strategical" planning, I don't think it's the proper place to discuss it. Here we're talking about FSharp.Core release, and the list Don mentioned is about FSharp.Core library additions / changes. It's not about language (or ecosystem for that matter) evolution. Although I'm not sure where we, the community, should discuss the language evolution strategy. Probably @cartermp could tell? |
This repository, but not this issue, is a potential place. But I'm not sure what would be gained by such a discussion. Evolution is a straightforward and well-defined process:
I don't see this process changing much. |
Having |
Closing old discussion - we've shipped a few FSharp.Core releases since now, and we're working towards what a 5.0 release of the library and language would look like on a per-feature basis, which I would expect in the fslang-suggestions repo |
The visualfsharp repo has a couple of pull requests for FSharp.Core. Before pulling these we wanted to pause for a moment and look at where we are with planning future additions, and get full community visibility and input on next steps.
Please discuss. Relevant resources are:
Proposal: 4.4.3.0 tactical release
It is proposed by @KevinRansom that we do a version 4.4.3.0 tactical release of FSharp.Core with at least the two PRs:
F# RFC FS-1028 - Implement Async.StartImmediateAsTask
F# 4.x: Add ToFSharpFunc overloads for Func<...>, especially for .NET Core
Add System.Collections.ICollection implementations to F# set/map
This seems reasonable. @KevinRansom would also like to publish incremental updates more frequently in the future (Again reasonable).
On the Slate
The top actionable requests are
a. add “task { … }”
b. add more immutable collections
c. improve interoperability with C#
Additional approved items of note:
a. string module enhancements
a. Deprecate the default definition of (!) and ask users to use .Value instead or use a compat module
b. Seq/Array/List.transpose
New requests:
Noting these requests not yet tracked by suggestions:
option { … }
andresult { … }
computation expressionsAsyncResultCell
(“TaskCompletionSource but for Async”)The text was updated successfully, but these errors were encountered: