-
Notifications
You must be signed in to change notification settings - Fork 53
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
Consider reviewing/updating F# library guidelines for 2019 #97
Comments
cc #96 |
Seems like this should mention FSharp.Core as follows (simplified): Unless you only want consumers of your library to be on the latest supported toolset, you will need to specify an explicit reference to FSharpCore: <PacakgeReference Update="FSharp.Core" Version="..."/> The version you choose should be based on the minimum F# language version you want to support. The minimum FSharp.Core version for each language version is listed below:
This tradeoff - features vs. reach - is an essential decision to make as a library author. |
@cartermp We should consider moving some of the material in http://fsharp.github.io/2014/09/19/fsharp-libraries.htmlacross into the Microsoft docs? |
We can, yeah. There is already a library author guidance guide here: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/ So the F# docs would not be a bad choice. |
The F# library guidelines from 2014 have served us fairly well. However they almost certainly now need updating to reflect changes and maturing of the F# ecosystem.
Discuss here.
cc @cartermp
The text was updated successfully, but these errors were encountered: