@BottomAll and @TopAll annotations

Compiling this code with the Map Key Checker fails:

public abstract class Parent<T> {
    public Parent(List<? super T> list) {}
}

public abstract class Child extends Parent<CharSequence> {
    public Child(List<? super CharSequence> list) {
        super(list);
    }
}

because the unannotated T in ? super T is interpreted as having the annotation for the actual type argument, which is CharSequence in Parent<CharSequence>, which is defaulted to @UnknownKeyFor. The T in ? super T needs to have the bottom type for the type system.

The programmer could explicitly annotate it for each type system, but that could get wordy and tedious.

Instead, we should create @BottomAll and @TopAll annotations (analogously to @PolyAll). These annotations only have an effect if a type does not have an explicit annotation for the particular type system. For example, a programmer could write @PreppyCheckerWearsPoloShirt @HipsterCheckerWearsSkinnyJeans @BottomAll which means the bottom annotation in every type system except the preppy and hipster type systems.

The @BottomAll and @TopAll annotations are intended to be written on wildcard bounds and possibly in other places.

Start by locating the existing @PolyAll annotation and the annotation definitions used by the Map Key Checker. Check how annotations on wildcard bounds are interpreted, then verify that @BottomAll and @TopAll provide defaults per type system while explicit annotations take precedence and the reported Parent/Child example compiles.