You're invited to contribute to future releases of the F# compiler, core library, and tools. Development of this repository can be done on any OS supported by .NET Core.
You will also need the latest .NET 5 SDK installed from here.
Build from the command line:
build.cmd
The build depends on an installation of Visual Studio. To build the compiler without this dependency use:
build.cmd -noVisualStudio
After it's finished, open either FSharp.sln or VisualFSharp.sln in your editor of choice. The latter solution is larger but includes the F# tools for Visual Studio and its associated infrastructure.
Build from the command line:
./build.sh
After it's finished, open FSharp.sln in your editor of choice.
-
See DEVGUIDE.md for more details on configurations for building the codebase. In practice, you only really need to run
build.cmd/build.sh. -
See TESTGUIDE.md for information about the various test suites in this codebase and how to run them individually.
-
The F# Documentation is the primary documentation for F#. The source for the content is here.
-
The F# Compiler Guide is essential reading for any larger contributions to the F# compiler codebase and contains links to learning videos, architecture diagrams and other resources. It also contains the public searchable docs for FSharp.Compiler.Service (or equivalent of Roslyn). The source for the content is in this repo under
docs/and the site is built automatically by this small repo. -
The F# Language Design Process is the fundamental design process for the language, from suggestions to completed RFCs. There are also tooling RFCs for some topics where cross-community co-operation and visibility is most useful.
-
The F# Language Specification is an in-depth description of the F# language. This is essential for understanding some behaviors of the F# compiler and some of the rules within the compiler codebase. For example, the order and way name resolution happens is specified here, which greatly impacts how the code in Name Resolutions works and why certain decisions are made.
Even if you find a single-character typo, we're happy to take the change! Although the codebase can feel daunting for beginners, we and other contributors are happy to help you along.
| Branch | Status |
|---|---|
| main |
Per-build versions of our NuGet packages are available via this URL: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json
These are the branches in use:
-
main- Almost all contributions go here.
- Able to be built, installed and used in the latest public Visual Studio release.
- May contain updated F# features and logic.
- Used to build nightly VSIX (see above).
-
release/dev15.9- Long-term servicing branch for VS 2017 update 15.9.x. We do not expect to service that release, but if we do, that's where the changes will go.
-
release/dev16.x- Latest release branch for the particular point release of Visual Studio.
- Incorporates features and fixes from main up to a particular branch point, then selective cherry-picks.
- May contain new features that depend on new things or fixes in the corresponding forthcoming Visual Studio release.
- Gets integrated back into main once the corresponding Visual Studio release is made.
Evolution of the F# language and core library follows a process spanning two additional repositories. The process is as follows:
- Use the F# language suggestions repo to search for ideas, vote on ones you like, submit new ideas, and discuss details with the F# community.
- Ideas that are "approved in principle" are eligible for a new RFC in the F# language design repo. This is where the technical specification and discussion of approved suggestions go.
- Implementations and testing of an RFC are submitted to this repository.
This project is subject to the MIT License. A copy of this license is in License.txt.
This project has adopted the Contributor Covenant code of conduct to clarify expected behavior in our community. You can read it at CODE_OF_CONDUCT.
Members of the F# Software Foundation are invited to the FSSF Slack. You can find support from other contributors in the #compiler and #editor-support channels.
Additionally, you can use the #fsharp tag on Twitter if you have general F# questions, including about this repository. Chances are you'll get multiple responses.
If you're curious about F# itself, check out these links: