Omar Kamel
Omar Kamel
Why exactly are we avoiding structural intersection types? It seems to me like a strictly useful feature. It is very useful for mixins, and of course normal promotions. after all,...
Where can we have a failed signature? I don't know of any case where dart allows you to have conflicting types of the same member name anywhere. By definition, any...
If we do want to avoid general type intersections, at least for this issue, we could keep it super simple. We *don't* intersect. Instead, it's about as useful as existing...
```dart class A { int get x = 42; } class B { int x() => 42; } ``` There is no way to implement both. It is not possible...
why _shouldnt_ it be breaking to add a new thrown type? its changing the behavior of the code isn't it? i _hate_ the idea that a package might just decide...
Ref: riverpod families
> `dynamicCapsule` Okay, but hear me out: `capsule.dynamic((use, arg) => ...)`
i'm against that particular example I would prefer, as stated here: https://github.com/dart-lang/language/issues/3680#issuecomment-2586206825 to instead use `late` for checking if something was passed. (possibly with `if (late? lateValue) lateValue = Value()`)...
Sure. Like I said, we might be okay with that - especially since the const values can't really have unexpected behavior due to the arguably inconsistent syntax. That's why I...
> The reason is likely that a nullable parameter, `({Foo? foo})`, and starting the function with `foo ??= createFoo();` is _good enough_, so the effort spent on allowing a non-constant...