Bob Nystrom

> It's about declaring a contract, like any interface is meant to. Our team can have a convention, when you create a new link you must extend AppLink, then the...

I think I understand what you're getting at. You think of abstract members as a human-facing "contract" that you want users to have to remember to implement when subclassing. From...

Yeah, I think capturing the "rest" elements would be useful. (And would naturally extend to actual rest parameters if we ever add that feature.) > We should probably keep our...

There is a lot going on here that I'm struggling to wrap my head around. I don't agree with: > Records don't really exist. They have no identity. They have...

OK, it sounds like we have consensus 🎉 . I believe Leaf will update https://github.com/dart-lang/language/pull/2489 to align with this in regards to record static type inference. I want to update...

> Idea: Allow `[]=` or `name=` to be used on expressions of tuple type, but _only_ in cascades. The result of such a cascade is a new tuple which has...

Ah, I like `.with()`. I think we would want this syntax to be high precedence, and using `.` sends that signal clearly.

I just discovered C# 9.0 [adds a similar `with` expression syntax](https://devblogs.microsoft.com/dotnet/welcome-to-c-9-0/) for their "record" types (which are more like Kotlin data classes than the record types here).

> This is, in my opinion, a must have. Everyone who ever programmed extensively in ML ended up writing their own [tuple update library](https://github.com/IntelLabs/flrc/blob/master/compiler/common/tuple.sml), and it was **the** feature that...

> I think all of the requests for adding data class `copyWith` style updates is pretty strong evidence that in fact incrementally updating classes is not well supported in Dart...