Loïc Denuzière

I published v0.24.38, it should fix this.

@BentTranberg The underscore syntax has already been implemented for F#8 as meaning `fun x -> x.firstName`, so unfortunately this would be ambiguous.

It looks like `open type` hasn't been considered. I think people will expect it to work, consistently with module-level `open type`, so the RFC should either include it, or explain...

Sounds good, although I think TimeSpan should use ToString() rather than TotalMilliseconds, it's quite readable. DateTimeOffset could be added too.

@brianrourkeboll Well, it only works for the second-to-last argument, otherwise the next "argument" will be inferred as a function to which you're passing the remaining arguments. Still a pretty cool...

Allowing `mutable` in patterns might be confusing, giving the false impression that it is a mutable reference into the object being matched. ```fsharp match myArray with | [| mutable x...

The casing thing is really unfortunate and artificially reduces the usefulness of this feature, but at the same time automatically uppercasing/lowercasing things in the language feels very wrong. In fact,...

These do feel more like lints than compiler warnings to me.

> Maybe we can allow arbitrary boolean/option-returning functions to be used in place of active patterns like in Haskell: This is already doable with APs, we could just add this...

> [@Tarmil](https://github.com/Tarmil) Pattern syntax cannot cover all expression syntax - see [#1018 (comment)](https://github.com/fsharp/fslang-suggestions/issues/1018#issuecomment-857885378) Sure, but that should be a separate issue. A solution that adds special syntax for full function...