Phillip Carter

An important distinction in the Rust docs: > Using `if let` means less typing, less indentation, and less boilerplate code. However, you lose the exhaustive checking that match enforces. Choosing...

The whole feature does sort of fall under the principle of not offering multiple ways to do the same thing, but it's not like this would be the first feature...

That's my primary concern with this feature. `if let` in isolation has prior art to look at and makes sense in isolation. But making it more complete leads us right...

I agree with @Tarmil, and to add to this: > I'm not completely against the idea of something like this, but I definitely don't like the specific proposed syntax. All...

> The advantages of making this adjustment to F# are increased language ergonomics and consistency as not being able to use byref in generics is purely a CLR restriction. Agreed...

Another con to this is that you can achieve this today by setting warnings as errors, though I can see someone wanting compile errors for failing to be exhaustive while...

Great discussion. Thinking about this at a bit more of a high level, there are two axes by which to grade a feature like this: * Does the enforcement feel...

@charlesroddie Colorization for disposable types is already implemented for F# - it just has the same default as C#: Here's what your sample looks like today if I change it...

See here: https://github.com/Microsoft/visualfsharp/issues/4618

> I cannot publish an F# app on the Windows Store. This is the never-ending saga of the awfulness that is the Windows Store and Win10 apps 😢. It's unsurprising...