Hey #fsharp - quick on the heels of #dotnet 8.0.300 releasing we have a new release of Ionide for VSCode to celebrate! This version's primary feature is updating the compiler and tools to the versions that ship with .NET SDK 8.0.300.

FsAutoComplete also includes a number of new code fixes and actions for managing signature files and using the new dot-lambda syntax. See the FsAutoComplete release notes at github.com/ionide/FsAutoComp… for more details.

Much like the Language Server Protocol brought re-use to editor tooling, allowing for Ionide to exist in many forms across VS Code, (neo)vim, emacs, and a host of other editors, the tree-sitter project aims to do the same for parsing text. It forms the basis for many tools,

from github search, to token highlighting in IDEs, and many more. More and more, a language needs to have a tree-sitter parser to participate in the modern tooling ecosystem. For this reason the @IonideProject org is happy to bring on github.com/ionide/tree-sitte… to the #fsharp family

Hey folks, today we're happy to officially adopt the #FsAutoComplete project as a member of the broader #Ionide tooling organization for #fsharp tools. While FSAC has been the backbone of the Ionide family of editor tools for many years now, it's lived in the fsharp GitHub org.

With this move to the Ionide org, we gain two things - clarity about the purpose of the fsharp org (housing language design and specs repositories) and a more consistent representation of the current maintainership of F# editor tooling all-up.

Are you interested in contributing to #fsharp @IonideProject or #FsAutoComplete but don't know how to start? Try asking #Copilot how to add a feature to the repository! Here's copilot showing how to add a new CodeFix, it does really well with very little guidance.