Lasse R.H. Nielsen

If we treat nullability specially, then: UP(A, B) := - let R = UP'(A, B) -- the one we use today, or better - if A

I will insist that adding a *warning* is *not* a breaking change. The point of having warnings, rather than errors, is that having warnings in a program is not an...

The purpose of `@override`, as I understand it, is to get warned if something I wrote doesn't actually override what I think it should override. I express the intent that...

I've actually reconsidered, and want to place `override` where `@override` is, not where `static` would be. It just feels better, IMO, to read `override external int foo()` than `external override...

The "must call super" feature is a different feature than "override". For one thing, it's on the super method, not the overriding method. I'm not sure it's a feature which...

An option is to make a missing `override` not be a warning or error at all, so you'd still need the `annotate_overrides` lint to get a warning. (Which then means...

If we warn about missing types on declarations that do not have an `override`, that would include *all* non-instance members, including `main`. Since override signature inheritance is the only way...

Avoiding F-bounded generics would be nice. It probably won't be enough with `Self` for that if you have mutually dependent types, like a built value and a builder. The `Self`...

I thought about an API like the `Token` thing, but decided against it. It's an extra overhead. If you *want* it, you can define your own `Token` class and collect...

You can creater a `gc"string"` prefix which is just the normal behavior for string interpolations, except that `toValue` returns the `.characters` of the string. ```dart class _GraphemeClusterInterpolator implements Interpolator {...