010bd0009a
* Added -compiler flag for build. Does not require VS to build. * Renamed -compiler to -noVisualStudio * Minor fix * Trying to fix unix builds * Update DEVGUIDE.md |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| .vscode | ||
| benchmarks | ||
| eng | ||
| fcs | ||
| mono | ||
| scripts | ||
| setup | ||
| src | ||
| tests | ||
| vsintegration | ||
| .gitattributes | ||
| .gitignore | ||
| .vsconfig | ||
| .vsts-signed.yaml | ||
| Build.cmd | ||
| CODE_OF_CONDUCT.md | ||
| CoordinateXlif.targets | ||
| DEVGUIDE.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| FSharp.Profiles.props | ||
| FSharp.sln | ||
| FSharpBuild.Directory.Build.props | ||
| FSharpBuild.Directory.Build.targets | ||
| FSharpTests.Directory.Build.props | ||
| FSharpTests.Directory.Build.targets | ||
| License.txt | ||
| Makefile | ||
| NuGet.config | ||
| README.md | ||
| Restore.cmd | ||
| RoslynPackageVersion.txt | ||
| TESTGUIDE.md | ||
| Test.cmd | ||
| VisualFSharp.sln | ||
| attributions.md | ||
| azure-pipelines.yml | ||
| build.sh | ||
| global.json | ||
| proto.proj | ||
| release-notes.md | ||
| restore.sh | ||
| test.sh | ||
README.md
The F# compiler, F# core library, and F# editor tools
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.
Contributing
Quickstart on Windows
Build from the command line:
build.cmd
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.
Quickstart on Linux or macOS
Build from the command line:
sh ./build.sh
After it's finished, open FSharp.sln in your editor of choice.
More options and information
See DEVGUIDE.md and TESTGUIDE.md for more details on additional configurations for building and testing, how to update compiler error messages, and more.
No contribution is too small
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.
Build Status
| Branch | Status |
|---|---|
| master |
Using nightly releases in Visual Studio
You can use the latest master build of the F# compiler and tools for Visual Studio via our nightly releases if you are a Visual Studio user. See details on setup here:
Even more nightly than the nightly
Alternatively, if you really want to live on the bleeding edge, you can set up a nightly feed for the Visual Studio preview releases, which use the latest commit in the preview branch. To do so, follow the same instructions as the above blog post, but instead with these links:
- Set your feed to the preview feed: https://dotnet.myget.org/F/fsharp-preview/vsix
- Install a VSIX manually from the preview feed: https://dotnet.myget.org/feed/fsharp-preview/package/vsix/VisualFSharp
Branches
These are the branches in use:
-
master- Most 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).
- Gets integrated into https://github.com/fsharp/fsharp to form the basis of Mono releases
- Gets integrated into https://github.com/fsharp/FSharp.Compiler.Service to form the basis of FSharp.Compiler.Service releases
-
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.
-
dev16.x- Latest release branch for the particular point release of Visual Studio.
- Incorporates features and fixes from master 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 master once the corresponding Visual Studio release is made.
F# language and core library evolution
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.
Additional project documentation
The following links can help you get an overview of some technical aspects of the F# language and compiler:
License
This project is subject to the MIT License. A copy of this license is in License.txt.
Code of Conduct
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.
Get In Touch
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.
About F#
If you're curious about F# itself, check out these links: