Paul Berry
Paul Berry
Looking at this a bit with @kallentu today, we ran across a bit of a thorny question that we should probably think hard about before we dive too deeply into...
> New breakage: Currently it's possible to add a member signature to a superclass, as long as it's compatible with all existing subclasses. If it becomes an error for the...
Capturing some discussion from yesterday's language meeting: A nice feature of this proposal is that since it becomes an error to place `override` on a declaration that doesn't actually override...
> The only real piece of pushback I have here is that this proposal removes the ability for an augmentation to add an explicit super constructor invocation. This was allowed...
> It seems like [Fixing type promotion failures](https://dart.dev/tools/non-promotion-reasons) might've been created separately because of how it interacts with analyzer tooling, is that accurate @stereotype441 or @bwilkerson (you both left feedback...
> Which of those diagnostic messages correlate to type promotion failures? Good question. In principle a lot of errors could result from a type promotion failure, but I would guess...
CC @johnniwinther
> If interpolation expressions are definitely thunkified, then they are not necessarily executed in order. That makes some cases harder to handle, like promotion in one expression affecting or not...
CC @dart-lang/language-team
> Would the user get a dead code warning if they were to instead add a meaningless "return" or "throw" after the switch? If not, that might be the best...