Lasse R.H. Nielsen

Doing case folding is non-trivial too. You need to know the file system of the individual path segments (with symbolic links, each segment can be on a different volume of...

Most likely reason is running a version of the analyzer that doesn't understand the enhanced deprecated. That would see `@Deprecated.implementation()` on `class RegExp`, see that it's an instance of `Deprecated`...

I guess all of the issues are parsing recovery artifacts. Annotations are not allowed on list elements at all, there is no valid parsing that starts with `[@`. That means...

Probably an oversight. There didn't use to be a reason to make an `enum` be generic before. After enhanced enum's, ` a` would be equivalent to `a()`, which is `a()`.

(Guessing here, I have no idea what the design or implementation of strict-inference is.) It looks like a bug that `[]` is not an error. > An empty collection literal...

The `list ?? {}` does an UP of `List` and `Set with a context type of `Iterable`. It correctly infers `{}`. For the UP of `List` and `List`, that's `List`...

You could report the `{}` as dead code. The entire body is unreachable (because to reach it you must first bind the `never` variable to a value of a subtype...

This looks like just plain old dead code. The rest of the expression continuation after the `throw` is definitely dead.

The `@Deprecated(...)` annotation was deliberately not made to be implicitly inherited by subclass members. That makes it possible to deprecate a method in a superclass, but keep the the methods...

How about making a member deprecated if it overrides a deprecated member *and* is marked with `@override`. Also make it a warning to override a deprecated member, have `@override` and...