The F# compiler, FSharp.Core library, and tools for F#
Перейти к файлу
Phillip Carter 7780047000
Be very literal about the LangVersion string (#7895)
* Be very literal about the LangVersion string

* Skip timing test
2019-11-21 20:59:11 -08:00
.github/ISSUE_TEMPLATE Update issue templates (#6784) 2019-05-20 18:09:51 -07:00
.vscode Port build.cmd to build.sh (#2497) 2017-02-28 10:26:58 -08:00
benchmarks normalize package version variables (#6733) 2019-05-14 14:16:38 -07:00
eng Update dependencies from https://github.com/dotnet/arcade build 20191119.6 2019-11-20 13:19:17 +00:00
fcs Remove unnecessary bash script from fcs (#7887) 2019-11-20 14:59:13 -08:00
mono convert to SDK projects 2018-12-03 09:48:42 -08:00
scripts fixes issue #6832 (#7259) 2019-07-24 18:08:15 -07:00
setup normalize package version variables (#6733) 2019-05-14 14:16:38 -07:00
src Be very literal about the LangVersion string (#7895) 2019-11-21 20:59:11 -08:00
tests Be very literal about the LangVersion string (#7895) 2019-11-21 20:59:11 -08:00
vsintegration typo: ahve -> have (#7648) 2019-09-27 12:59:52 -07:00
.gitattributes replace deprecated nuspec `iconUrl` element with `icon` 2019-09-27 13:56:28 -07:00
.gitignore Ignore Mac trash (#7729) 2019-10-14 17:08:03 -07:00
.vsconfig Trim vsconfig (#6789) 2019-05-21 11:54:25 -07:00
Build.cmd consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
CODE_OF_CONDUCT.md Update several links (#7055) 2019-06-25 10:13:01 +01:00
CoordinateXlif.targets Fix Xlif issue (#5995) 2018-12-07 17:43:35 -08:00
DEVGUIDE.md Merge remote-tracking branch 'upstream/release/dev16.3' into merges/release/dev16.3-to-master 2019-09-23 15:01:37 -07:00
Directory.Build.props consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
Directory.Build.targets consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
FSharp.Profiles.props Merge remote-tracking branch 'upstream/release/dev16.3' into merges/release/dev16.3-to-master 2019-09-23 15:01:37 -07:00
FSharp.sln add FSharp.Compiler.Scripting (#7437) 2019-08-23 15:37:41 -07:00
FSharpBuild.Directory.Build.props [master] Update dependencies from dotnet/arcade (#7706) 2019-11-05 15:18:09 -08:00
FSharpBuild.Directory.Build.targets ensure Microsoft.FSharp.NetSdk.props makes it into VisualFSharpFull.vsix (#6942) 2019-06-05 14:13:46 -07:00
FSharpTests.Directory.Build.props Apparently the unit test dll's don't use fsharptest.directory.props (#7115) 2019-07-03 15:05:14 -07:00
FSharpTests.Directory.Build.targets fsi, correct error messages 2019-07-04 01:35:38 -07:00
INTERNAL.md add doc with links to all internal build definitions, etc. (#7505) 2019-09-05 21:37:39 -07:00
License.txt Adopt the MIT License (#3517) 2017-08-31 16:02:26 -07:00
Makefile Netstandard2 (#6814) 2019-05-25 12:40:29 -07:00
NuGet.config update package feed url (#7468) 2019-08-29 14:45:40 -07:00
README.md Updates README with new non-vs-dependent build switch. (#7565) 2019-09-16 10:05:38 -07:00
Restore.cmd consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
RoslynPackageVersion.txt Roslyn Shim - Round 2 (#6734) 2019-06-13 12:14:13 -07:00
TESTGUIDE.md update perl test runner (#7779) 2019-10-30 15:26:33 -07:00
Test.cmd consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
VisualFSharp.sln add FSharp.Compiler.Scripting (#7437) 2019-08-23 15:37:41 -07:00
attributions.md Update attributions.md (#3490) 2017-08-23 10:36:26 -07:00
azure-pipelines.yml Update FCS build to using .Net Core only (#7883) 2019-11-20 13:27:35 -08:00
build.sh Merge remote-tracking branch 'upstream/dev16.0' into merges/dev16.0-to-master 2019-04-04 15:20:07 -07:00
global.json Update dependencies from https://github.com/dotnet/arcade build 20191119.6 2019-11-20 13:19:17 +00:00
icon.png [master] Update dependencies from dotnet/arcade (#7706) 2019-11-05 15:18:09 -08:00
proto.proj Added -noVisualStudio flag for build.cmd. (#7071) 2019-06-27 18:16:04 -07:00
release-notes.md Update several links (#7055) 2019-06-25 10:13:01 +01:00
restore.sh consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00
test.sh consume dotnet arcade sdk 2019-03-21 11:49:18 -07:00

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: