BreyerW

> The other question is whether readonly violations should fall under the same umbrella. Generally readonly is there for memory safety reasons, ensuring a piece of memory is not written...

Do we really need new constraint for that though? By ref structs cannot implement interfaces anyway if i remember correctly (and object -derived methods are expected to throw anyway) so...

Maybe `var s = _ into () => { return 42; };` instead

> ### Allow `ref` auto properties? > Support `ref` auto property declarations? If so, allow `set` or `init`? > > ```cs > ref T P0 { get; } > ref...

According to linked proposal document it is purely compiler magic. It is mentioned that compiler will spit two methods instead of one. One virtual override and another who will call...

I like `must` since it flows naturally with `set` and `init` `required` kind of doesnt flow (linguistically) with these two keywords but is useable on property itself not just acessor...

@lambdageek Recommended way to implement operators was always that you provide normal method that actually implements operator and call that method in operator. So for your example you would implement...

I would like to say that `break` as sort of return statement is very confusing. `yield` is much better imo.

The difference is that `break` never returned value just broke current control, now it will. While `yield` USUALLY return value and in case you wanted to leave control without returning...

> If `return` is off the table, `yield return x` feels better than `break x`, IMHO. I think this is off table too because `yield return` is already valid in...