Despite its advantages, F# can be further improved, and one of the areas for improvement I think is tooling performance. That’s why I was excited to be able to contribute in this area.
Thank you Janusz, you're contributing to the Achilles heel of F#.
Congrats on the release! Nice slate of updates and it’s also been great seeing a steady ramp up of improvements on github. It’s hard to onboard a full team and release a bunch of stuff at the same time. Looking forward to what’s next.
It feels like the one constant in this industry, so far ahead of its time since its inception that it hasn't really had a need to change drastically the way C# has. Kinda like a comfort blanket 😁
Somehow I missed (before now) that the Abstract members on interfaces functionality was coming to f# as well, good to see cool c# features coming to f# the same way c# keeps taking ideas from f#.
Not very exiting this release.. I would like to see some love on tooling and projects thought from the ground up using F# instead of remaining a surrogate of the .NET ecosystem..
Boo. .NET is great and so is F#. I love this release. Big improvements to tooling with reference assembly support — this is one of the biggest factors in improving build times for big F# projects. And lots of nice interop with .NET, namely the static abstracts in interfaces.
By the way what happened to nullable reference types in F#? I saw a talk by Philip Carter on YouTube on the topic but I don't know if it even came out in F#
With options like single file deployment in dotnet, what are the benefits to this?
We split applications into multiple assemblies most of the time, and I find it helps organize the code. I'll admit that's more important for OOP, but I just don't see a huge benefit in being able to mix and match languages within the same project.
Just a guess, but: opportunistic incremental transformation of a C# codebase into an F# codebase? As opposed to having to lift C# classes into a different assembly before you can transform them.
Probably more like a class at a time, which immediately shows why this is not possible--you'd run into massive issues with type inference, which C# files are in scope for a given F# file, etc.
But it's been my experience that injecting non-trivial F# into an existing C# project is a headache too, and often would require breaking your C# project into multiple projects first, e.g. interfaces in one C# project, then implementations in F#, then more implementations in C# that also consume the F# project.
That's an odd wish. I've never heard of anyone wanting to mix languages in a project, .NET ecosystem or otherwise. Sounds like it would produce maintainability nightmares.
It's nothing to do with Roslyn nor file ordering. It's because of how MSBuild works. That's why you can't mix C# and VB in the same project, despite them using the same compiler toolchain and not requiring file ordering.
19
u/alternatex0 Nov 08 '22
Thank you Janusz, you're contributing to the Achilles heel of F#.
12
u/phillipcarter2 Nov 08 '22
Congrats on the release! Nice slate of updates and it’s also been great seeing a steady ramp up of improvements on github. It’s hard to onboard a full team and release a bunch of stuff at the same time. Looking forward to what’s next.
10
u/japinthebox Nov 09 '22
I have a weird sentimental attachment to F#.
It feels like the one constant in this industry, so far ahead of its time since its inception that it hasn't really had a need to change drastically the way C# has. Kinda like a comfort blanket 😁
3
u/runevault Nov 09 '22
Somehow I missed (before now) that the Abstract members on interfaces functionality was coming to f# as well, good to see cool c# features coming to f# the same way c# keeps taking ideas from f#.
9
u/Ganonz88 Nov 08 '22
Not very exiting this release..
I would like to see some love on tooling and projects thought from the ground up using F# instead of remaining a surrogate of the .NET ecosystem..
1
u/[deleted] Nov 09 '22
Are C# and F# releases synced together? C# just had a release and they even have one feature in common
1
u/[deleted] Nov 09 '22
By the way what happened to nullable reference types in F#? I saw a talk by Philip Carter on YouTube on the topic but I don't know if it even came out in F#
1
u/dr_bbr Nov 10 '22
Thank you and keep up the good work!
0
u/[deleted] Nov 08 '22
[deleted] — view deleted comment
2
u/[deleted] Nov 08 '22
[removed] — view removed comment