orthoxerox

Why is it tentatively planned for 7.2 if records themselves are in 8.0?

@alrz this will change `with` from a purely syntactic transformation like LINQ query expressions to a more involved one.

@alrz > Actually the pattern-based with is not that simple since we first need caller-receiver default-argument (mentioned in the records proposal) to substitute absent init values But this will get...

I think the natural type of the new syntax should be `List`, not `T[]`. Arrays already have their own creation syntax and lists are used much more often than bare...

@MI3Guy could you please give an example? @gafter has mentioned variance in the original issue as well, but I find it hard to wrap my mind around the idea.

Well, `bottom` is its official name in type theory, but since we call futures tasks I don't mind it being called `never`.

@mattwar 1. It will allow to explicitly mark functions that never return. This will potentially allow CLR to reuse the frame on the call stack if someone writes (or automatically...

Will there be a type that represents potentially *invalid* UTF-8 strings, like Linux file paths?

@gafter will `System.IO` classes use `ReadOnlySpan`? Like, `IEnumerable System.IO.Directory.EnumerateFiles(ReadOnlySpan path)`?

Roles feel like they need a validator method, something that is invoked to by the "implicit conversion" to ensure that the underlying object can fill in that role. I'm not...