Don Syme
Don Syme
> Would the attribute imply structural equality, would such a class otherwise be indistinguishable from a bona fide record? The type would have to implement the equality/comparison interfaces
> Why not all expressions?? At a high level it would be ideal to accept all expressions. However this would not be backwards compatible. The F# pattern syntax is a...
> @dsyme I don't think you can put patterns when expressions are expected (active pattern inputs) At the parser level, this isn't the case - almost, but not quite. This...
> Are pattern syntaxes and expression syntaxes mutually exclusive? Yes, there are enough small differences that's not possible. In retrospect I may have unified these syntaxes originally. However there are...
> What about interpolated strings? Yes, they should be added to the available expressions.
Marking as approved-in-principle because there are definite cases that should be allowed, as described above.
@robkuz No, that's tracked by a different suggestion
RFC is here: https://github.com/fsharp/fslang-suggestions/issues/212
@bbatsov I've also sent a message to Tomas. You and @IanWitham might like to also join the core team at Amplifying F#, who I can highly recommend https://amplifyingfsharp.io/. They're really...
You do this: ```fsharp type IFoo = abstract Bar1: int -> int abstract Bar2: int -> int -> int type Foo() = interface IFoo with member x.Bar1 a = (x...