Skip to content
The F# compiler, FSharp.Core library, and tools for F#
F# C# Rich Text Format Visual Basic Perl PowerShell Other
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue templates (#6784) May 21, 2019
.vscode Port build.cmd to build.sh (#2497) Feb 28, 2017
benchmarks normalize package version variables (#6733) May 14, 2019
eng only install 2.1 SDK in non source build scenarios (#7703) Oct 4, 2019
fcs replace deprecated nuspec `iconUrl` element with `icon` Sep 27, 2019
mono convert to SDK projects Dec 3, 2018
scripts fixes issue #6832 (#7259) Jul 25, 2019
setup normalize package version variables (#6733) May 14, 2019
src allow fsi evaluations to be cancelled (#7736) Oct 18, 2019
tests allow fsi evaluations to be cancelled (#7736) Oct 18, 2019
vsintegration typo: ahve -> have (#7648) Sep 27, 2019
.gitattributes replace deprecated nuspec `iconUrl` element with `icon` Sep 27, 2019
.gitignore Ignore Mac trash (#7729) Oct 15, 2019
.vsconfig Trim vsconfig (#6789) May 21, 2019
Build.cmd consume dotnet arcade sdk Mar 21, 2019
CODE_OF_CONDUCT.md Update several links (#7055) Jun 25, 2019
CoordinateXlif.targets Fix Xlif issue (#5995) Dec 8, 2018
DEVGUIDE.md Merge remote-tracking branch 'upstream/release/dev16.3' into merges/r… Sep 23, 2019
Directory.Build.props consume dotnet arcade sdk Mar 21, 2019
Directory.Build.targets consume dotnet arcade sdk Mar 21, 2019
FSharp.Profiles.props Merge remote-tracking branch 'upstream/release/dev16.3' into merges/r… Sep 23, 2019
FSharp.sln add FSharp.Compiler.Scripting (#7437) Aug 23, 2019
FSharpBuild.Directory.Build.props merge Jul 26, 2019
FSharpBuild.Directory.Build.targets ensure Microsoft.FSharp.NetSdk.props makes it into VisualFSharpFull.v… Jun 5, 2019
FSharpTests.Directory.Build.props Apparently the unit test dll's don't use fsharptest.directory.props (#… Jul 3, 2019
FSharpTests.Directory.Build.targets fsi, correct error messages Jul 4, 2019
INTERNAL.md add doc with links to all internal build definitions, etc. (#7505) Sep 6, 2019
License.txt Adopt the MIT License (#3517) Aug 31, 2017
Makefile Netstandard2 (#6814) May 25, 2019
NuGet.config update package feed url (#7459) Aug 28, 2019
README.md Updates README with new non-vs-dependent build switch. (#7565) Sep 16, 2019
Restore.cmd consume dotnet arcade sdk Mar 21, 2019
RoslynPackageVersion.txt Roslyn Shim - Round 2 (#6734) Jun 13, 2019
TESTGUIDE.md Update repo name (#6951) Jun 7, 2019
Test.cmd consume dotnet arcade sdk Mar 21, 2019
VisualFSharp.sln add FSharp.Compiler.Scripting (#7437) Aug 23, 2019
attributions.md Update attributions.md (#3490) Aug 23, 2017
azure-pipelines.yml Disable Linux_FCS (#7697) Oct 3, 2019
build.sh Merge remote-tracking branch 'upstream/dev16.0' into merges/dev16.0-t… Apr 4, 2019
global.json Merge pull request #7666 from dotnet/darc-master-e0c9f4bf-0d57-4f79-a… Oct 4, 2019
proto.proj Added -noVisualStudio flag for build.cmd. (#7071) Jun 28, 2019
release-notes.md Update several links (#7055) Jun 25, 2019
restore.sh consume dotnet arcade sdk Mar 21, 2019
test.sh consume dotnet arcade sdk Mar 21, 2019

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

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.

Quickstart on Linux or macOS

Build from the command line:

./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 Build Status

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:

https://blogs.msdn.microsoft.com/dotnet/2017/03/14/announcing-nightly-releases-for-the-visual-f-tools/

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:

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:

  1. 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.
  2. 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.
  3. 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:

You can’t perform that action at this time.