4 ms·
> Ah and don't expect Code Generators to ever support F#. What sort of Code Generators are we talking? I ask because I have a very early alpha project that do
by dpwm 6y ago
> Ah and don't expect Code Generators to ever support F#.
What sort of Code Generators are we talking?
I ask because I have a very early alpha project that does F# code generation using Fantomas. Apart from an (uninvestigated) slightly higher startup time than I hoped for, it seems fine.
- pjmlp 6y agoThe ones in .NET 5 and .NET 6, integrated into Roslyn and a key part of the upcoming AOT support. https://devblogs.microsoft.com/dotnet/introducing-c-source-generators/ https://devblogs.microsoft.com/dotnet/introducing-c-source-g... The main goal is for them to be the .NET version of Java's annotation processors and thus allow many libraries to replace their reflection code with compile time code generation.
- dpwm 6y agoOh wow, thanks for that. I’m new to .NET and didn’t know anything about Source Generators. That seems to be a pretty interesting feature. I followed the link to the F# suggestions and found https://github.com/fsharp/fslang-suggestions/issues/864 https://github.com/fsharp/fslang-suggestions/issues/864 It seems like there is interest but with a "let’s wait and see what happens with C#" kind of approach. I’ll admit it looks far off, but there appears to be interest. I’m certainly not expecting them, and for my purposes F# provides more than enough anyway. I am nonetheless interested: why do you think they will never come to F#?
- pjmlp 6y agoBecause Roslyn compiiler stack is only for C# and VB, F# has its own infrastructure. Until now, all the F# related tooling tends to be done by a mix of the tiny MS team and FOSS community, it is not the full steam rolling engine that C# and VB get.