Tomas Grosup
Tomas Grosup
@copilot You are a liar, the issue is not pre-existing, you have caused it. Its just that your contrainer's bootstrap F# compiler already has it. Also, your code changes are...
@copilot : /home/vsts/work/1/s/src/Compiler/Checking/Expressions/CheckExpressions.fs(7318,85): error FS0001: The type 'range' does not match the type 'Val option'
For F# DUs which also implement IEnumrable, S.T.J could use IEnumerableDefaultConverter perharps? Right now, F# DUs are not supported, no matter what the interface. (even though Lists and Options are...
It is a leaky abstraction due to loss of type (`obj`). So even though the compile-time type is just `seq` and that should work, the loss of types means that...
I really think this has to do with something (S.T.J. most likely, being used by aspnetcore) using a runtime detection. And when it sees an F# DU at runtime (even...
> But, the bottom line is still for me that if Seq.empty did not internally happen to be implemented as an interface on a DU, we would not be having...
> "F# has a funny internal wart that happens to cause a real problem for a real usage". If you look at the generated IL, it's just a plain empty...
Would it be possible to try that as a standalone .fsproj with references to existing files up to the SyntaxTree folder (and removing what is not needed) ? If there...
I think there is more value to this proposal - while on the call with @Martin521 and @baronfel on the possibility of having "dotnet run app.fs" supported in the .NET...
/run ilverify