Will Smith
Will Smith
Another example for the same effect: ```fsharp let inline plus< ^T1, ^T2, ^T3 when (^T1 or ^T2) : (static member (+) : ^T1 * ^T2 -> ^T3)> (x: ^T1) (y:...
Good find and very interesting. This is a result of the optimizer. For inline functions, if the optimizer sees a conditional where it knows at compile time will only ever...
This is after type inference, so that shouldn't be doing anything. At a high-level, this is like the flow of the compiler: `Parsing -> TypeChecking -> PostInferenceChecks -> Optimizer ->...
Seems I'm wrong a bit on this. The issue is more complex than I thought. Hard to tell who the real culprit is. I have another repro that will give...
I agree that the error showing the type of the value would be beneficial. I did a quick look at this. It seemed simple enough because the error information does...
Can confirm, happens when compiling as Debug in VS. Release seems to work though.
@auslavs This is a compiler bug and should compile and run successfully. I will spend time on resolving it this week.
So, @auslavs , the error you have is similar to the one reported here, but the cause is very different. I have a fix for your issue: https://github.com/dotnet/fsharp/pull/8287 Regarding this...
> Perhaps we could add some metadata to these merged types (maybe a new attribute), which would make the `FSharp.Reflection` experience transparent from the developer's perspective. This seems very reasonable...
This does seem like a bug, here is another example that is smaller but has the same issue: ```fsharp type Test