Don Syme
Don Syme
> and seems to be owing to that very sharp divide made of deciding immediately whether a given identifier belongs to a Property or a Method on a type. Both...
I believe the difference between C# and F# is that C# see `table.Width(100)`, decides it is a method call (though it could be an invoke of a delegate-valued property), so...
It's unfortunate. C# only supports extension methods. It always prefers methods on the original type. But if there's a property with that name, it doesn't care and prefers the extension...
@abelbraaksma Here's the current situation: The constraint solver engine of F# has no ability to represent constraints of this form - constraints "T :> U" are solved to "T =...
@wallymathieu I've edited my comment to clarify it
I'm marking this as approved in principle because it's reasonable that it is possible to at least define, and, in some cases, use these methods in F#. However it's not...
Could you paste some screen shots? thanks
There are definite improvements here which we can lift straight in - especially to the messaging in "Getting Started". I won't pull it directly but will take that wording and...
> There are definite improvements here which we can lift straight in - especially to the messaging in "Getting Started". I won't pull it directly but will take that wording...
Note F# does let you use `ReflectedDefinition` attribute on method parameters, e.g. ```fsharp type B() = static member M([] x: Quotations.Expr) = printfn "x = %A" x B.M(1+1) ``` gives...