Lasse R.H. Nielsen

Agree! And double quotes for auto-added imports.

The warning seems unnecessary, but the cast isn't actually *working*, so some warning is warranted. You have an `RxList`, which I assume is *not* an `RxList` (because then you could...

Do we currently give a warning if the annotation is used in null-safe code? If so, we could consider it effectively deprecated, and just remove it in a version of...

One possible alternative is to use the quoting of existing imports, if there are any, and only fall back on single quotes if there are no imports at all.

We should not have any deprecated APIs that survive a major version increment, so would it suffice to simply consider all deprecated declarations as errors? (Would that just be the...

I like the idea of making it per-package. I'd even drop a having a special flag for the SDK, and just treat it as a package named `dart`, so you...

If this feature is useful to us, it's probably useful to others as well. Other people don't make SDKs, so the thing they version are packages. The corresponding problem would...

Initial opinion: I prefer the `view` approach to static views, to the `extension struct` approach.

What if we treat `extension struct` not as a variant of a `struct`, but as a variant of an `extension` (an extension of extension, really). That means using `extension` notation:...

>> but being a subtype does not mean having the same signature. It means being usable _at_ the supertype, not _as_ the supertype. > I don't know what you mean...