Don Syme
Don Syme
I agree with @forki that the project has now really become "the opinionated template for F# community projects". Not sure you intended that @pblasucci but it's a great thing :)...
Hi @forki, could you add the "GitHub releases" to the most important F# community projects first, e.g. FSharp.Data and FSharp.Compiler.Service and maybe a few others? Just so we get a...
Yes, I noticed that too
I've started an RFC discussing how to get F# analyzers incorporated into FSHarp.Compiler.Service, i.e. available in all F# tooling https://github.com/fsharp/fslang-design/blob/master/tooling/FST-1033-analyzers.md The main issue is binary compatibility for the information being...
See also https://github.com/ionide/FSharp.Analyzers.SDK/issues/28
> @dsyme Can we have fixes as lazy (similar to FSharpLint)? Yes I've mentioned that in the RFC
It might, yes - it partly depends how often we revise the API, whether an analysis application can host mutiple versions (do we use naming `FSharp.Compiler.Analysis.v1.0`, `FSharp.Compiler.Analysis.v2.0` etc.), and who...
I'll link this discussion in the RFC (am happy to keep discussing here)
It's curious that one way to make the Analyzer API both binary compatible and simple and stable and extensible would be to transact all context information via an untyped format...
My interest in this is partly for the shape checking tooling for DiffSharp, which roughly speaking needs nothing more than the compilation arguments and ISourceText - it's happy to do...