Don Syme

All that's needed to implement this is adding the appropriate lines here: ```fsharp arrayTypeSuffix: | LBRACK RBRACK { 1 } | LBRACK COMMA RBRACK { 2 } | LBRACK COMMA...

Separately I noticed we hit an error path "rankOfArrayTyconRef: unsupported array rank" in hover tips in the IDE when defining these type abbreviations: ```fsharp type 'T array5d = 'T ``[,,,,]``...

Jagged arrays should not have changed printing with 13700, it would be a mistake if they have

I'm still getting this on .NET 6 ``` C:\GitHub\dsyme\fsharp>artifacts\bin\fsi\Debug\net6.0\fsi.exe Microsoft (R) F# Interactive version 12.0.0.0 for F# 6.0 Copyright (c) Microsoft Corporation. All Rights Reserved. For help type #help;; >...

I notice the .NET docs have a mechanism for specifying F1 keyword targets, e.g. ``` f1_keywords: - let!_FS ``` We could perhaps add long lists of the necessary forwarding tokens...

I posted a question here https://github.com/dotnet/dotnet-api-docs/issues/7724 but got no reply as yet

I see what's happening now - this is actually hitting a deprecated feature that is only giving a warning - we resolve `Foo.Bar` to the union case but give a...

I've added #13182 to give an error for the deprecated feature. This will allow us in some subsequent version to give the adjusted name resolution.

I don't quite understand the likely nature of the bug from the above > Calling and cancelling it like this may lead to situation where two scrips closures are calculated...

Looks like FSharpDependencyManager is allowing multiple concurrent callers to attempt resolutions within its working directory at the same time