Gauthier Segay

@palladin thanks for your feedback. No I don't have plans at this stage for cloud deployed app, I'm far from that for my current use case. Do you have an...

@eiriktsarpalis thanks for additional feedback. In my current use case, I'm not looking for "persistable" and the "fault tolerant" aspect implies the process stays up but not looking for further...

@isaacabraham thanks, I'll check what Azure Stack is about (I remember seeing anouncement back then). I hope it is lightweight enough, ultimately this would need to ship in our setup...

I've noticed that with type providers in general, should we open an issue on [Microsoft/visualfsharp](https://github.com/Microsoft/visualfsharp/) so that the type provider infrastructure gets ability to surface additional dependencies for msbuild tasks?

Would this be hard to fix? I think it is a significant usability problem as it is not obvious which piece of which template makes this happen.

@plule, note that I'm pretty much newbie with rust, nor familiar with faust, but thanks for prompting. To me the solution 3 seems great: * the crate seems to handle...

related on dotnet/fsharp: #1254, #2503 related on dotnet/roslyn: !!???! (is there a matching ticket, for F# 1.0 interop on C# & VB.NET side?) related on CLR languages: profit

Around nullness checking, performance and F# codebases that are already null safer than industry average since V1. Is there going to be a "experimental F# SPO optimizer" version, that is...

knowing: * considerations allegedly taken for tailoring the tree shaking story * the team behind the compiler (apt to take any ticket from runtime and deal with it, maybe it...

Related: #11564 (remove setter for init only properties)