-
Couldn't load subscription status.
- Fork 833
Description
Overarching priorities until the .NET 5 release
This list represents our overall priorities that go beyond a particular sprint. The intention isn't to track items that we can call "complete". Instead, they represent what we view as generally important to focus on.
- Fix any high-priority bugs or regressions
- Release a great F# 5 alongside .NET 5
- Continue to invest in the performance and stability of Visual Studio tooling for F#
- Ensure there is a great experience for F# in .NET Interactive and Jupyter Notebooks
- Support the F# OSS community by reviewing their contributions and helping them along
- Improve our testing infrastructure
- Improve our infrastructure
Focus items for this 3 week(ish) period
This set of lists represents what we're working on now, and hope to accomplish. Nothing here is guaranteed to be accomplished by a given date, since we will only merge and ship changes when they have an appropriate high level of quality. Sometimes things are easier than they seem, and sometimes they are harder.
Previous period: #9411
F# 5
- Complete the open type declarations implementation - @TIHan
- Complete the
nameofimplementation - @dsyme - Address design questions/issues in string interpolation - @dsyme
- Finish design for unamanged generic constraints - @vzarytovskii
- FSharp.Core is .NET Standard 2.0 only - @KevinRansom
- Remove the preview attribute from non-slicing APIs in FSharp.Core - @KevinRansom
Core F#
- Investigate F# .dll loading issues in Visual Studio for low-memory scenarios - @KevinRansom
- Investigate/plan a fix for DependencyManager/AssemblyLoadContext to unlock .NET Standard 2.0 FCS (FCS solution tests fail on Mono #8766) - @KevinRansom and @auduchinok
- Modernize Type Provider SDK to be .NET Standard only ([okay to merge now] - move to .NET Standard exclusively fsprojects/FSharp.TypeProviders.SDK#339) - @cartermp
- Investigate how to make
#r "nuget:"not lazy - @KevinRansom - Pull in FCS with aims to publish from this repo - @KevinRansom @brettfo
F# support in .NET Interactive and Jupyter Notebooks scenarios
- Progress in F# completion in VSCode notebooks
- Draft RFC for
#!nugetfor .NET Interactive (Oddities with FSI package management #9270) - @KevinRansom and @cartermp
Infrastructure
- Fluent F# assertions framework for compiler test suite - @vzarytovskii
- Test modernization progress - @vzarytovskii
Rough prioritized backlog
This list of items represents things we are very much planning on completing. However, they are not planned for this sprint specifically. If we complete items above or are blocked on them, we intend on focusing on these issues. This list is not exhaustive.
- Complete work for Extensions and Constraints ([RFC FS-1043] Extension members visible to trait constraints #6805)- @dsyme
- Support for
#r "project"- @cartermp, @KevinRansom, community - Editor performance with
#r "nuget"- @KevinRansom - FSharp.Compiler.Service is .NET Standard 2.0 only (incorporate @baronfel's work move FCS to netstandard2.0 and purge old net461 related code #7888) - @cartermp, @KevinRansom
- Publish FSharp.Compiler.Service from this repository (Properly incorporate FCS into the build and publish pipeline #9457) - @KevinRansom, @cartermp, community
- Remove the desktop compiler from our build, producing on a CoreCLR-based compiler and FSI - @KevinRansom
- Add support for .NET Interactive extensibility in XPlot - @cartermp