Lasse R.H. Nielsen

Not sure how you would efficiently assert that there is only one reference to each object in the object graph. That sounds like something which needs a full GC-equivalent memory...

Using `allocateForTransfer` would probably be zone-based, otherwise it won't work with `async` functions. Using a separate page with a write barrier needs to check both directions: When references to the...

@devoncarew @mit-mit

There are probably may places you can mention the class, and still use this optimization. What if a class is definitely uninstantiated (its private, there are no invocations of its...

Use `List.empty`. If we ever get to remove the `List` constructor, then after a while we might choose to repurpose. Until then `List.empty` is the constructor to create an empty...

We could remove the parameter of `List` when we release Dart 3.0, and keep the constructor with no argument creating an empty growable list. It's not really *necessary*. The canonical...

@Lelelo1 I assume you refer to the `growable` parameter of `List.empty`. It actually does make sense to create unmodifiable empty lists of a specific type. Some algorithms creates a new...

I'm not on the analyzer team, so I wouldn't be able to answer that. Let's see if the analyzer team has a comment.

While tempting, I fear that it won't be enough in practice, and I think that such a very specific rule isn't worth its own weight. (The analyzer implementors are obviously...

Say there exists a `class D implements B, C {}` (and perhaps several other unrelated subtypes of both `A` and `C`), and you know, for some reason, that `a` *is*...