Michael Bacarella

Results 44 comments of Michael Bacarella

I actually can't induce my version to fail on a blank line. It never shows an error message. `F# Formatting` is not even available in the dropdown. I did notice...

`dotnet --version` yields `7.0.200`. Which is interesting because NET7.0 is not available as an option in the VS2022 project settings dropdown. My project does not have a `global.json` file.

Just did those. Now shows this: ``` dotnet tool list Package Id Version Commands Manifest ------------------------------------------------------------------------------------------------------------ fantomas 5.2.1 fantomas C:\Users\mbac3\projects\giraffe-example\.config\dotnet-tools.json ``` So, closing and restarting VS2022 and reformatting the code...

Yup. # Running from CLI ![minimal_good](https://user-images.githubusercontent.com/135031/220398615-a7572071-2e5f-4c60-8c96-f208254a327a.png) # Running from VS2022 ## Before format ![minimal_bad_before](https://user-images.githubusercontent.com/135031/220398752-a8a0c0ec-38b4-4439-a128-406871e2b234.png) ## After format ![minimal_bad_after](https://user-images.githubusercontent.com/135031/220398821-c1458319-f9e7-4fa3-9262-0a107cb07dd1.png) 🤔

Sure. ```fsharp cat .\script.fsx #r "nuget: Fantomas.Client, 0.8.0" open System open System.IO open Fantomas.Client.Contracts open Fantomas.Client.LSPFantomasService let service : FantomasService = new LSPFantomasService() // this path needs to be absolute...

Firstly I'd like to say I'm really excited about multicore since it speeds up *interactive* application performance use-cases quite nicely in initial tests. My hands were shaking from excitement when...

Hi @kayceesrk, that sounds like it would suffice, yes.

seems fine, thanks! be sure to add yourself to the CHANGES.md. I'd make an "UNRELEASED" header entry.

I offer to do it though, one question: users may resent the small performance penalty this imposes without some kind of flag to undo it, aside from the semantics concern....