Tomas Grosup

I think it makes sense to think about constraints and anti-constraints ("allows ref struct") separately in the context of a possible design. In the new proposal, if the constraints are...

If you would do a type augmentation for Seq, and the generic code would not be typechecked for meeting "allows ref struct" criteria, what would happen if someone tries to...

`#if` for the constraint definition if augmenting a type that has different definitions across the TFM targets, I am afraid I do not have a better proposal here.

I will mark this as approved in principle, but needing an RFC - the design must consider both constraints as well as anti-constraints and ensure correctness of generated code. It...

> Is this why for example you have to use dummy types in SRTP for things like this? Apologies for any grossness in the code it's just a copy paste...

I will mark the version for specifying a different visibility for the constructor as approved in principle. The reasons/bugs Don listed from F# 1. are coming from a different and...

You are right with classes here, and we do have orthogonal proposals for moving language features to classes ( with syntax, equality. Pattern matching likely not though...). For a "static"...

What is the main difference to an `if let` ? `match` has the existing connotation for doing exhaustive matching. The conditions for typechecking such expression- either `unit` returning or used...

Is the semantics effectively to "slice" a single property (get,set and including any possible behavior attached, e.g. INotifyPropertyChanged) into a new single purpose object, similar to a `Lens` but with...

I see, thank you for the detailed elaboration. The concept based down to a closure of the original data and exposure of `get/set` members. There are `Lens` inspired libraries or...