It's definitely a mistake that we do nothing here.
There are two options. The obvious is to simply raise a raw warning;
this is a straightforward spec/impl fix which we can easily do.
The other option is to do as we did with method refs, where we apply
type inference to an unadorned `Foo` pa
Hi, currently when there is an instanceof + type pattern with a raw type,
javec doesn't raise any warning (oops), worst it compiles because i believe it
should not, but for that, the spec has to be amended.
interface Foo {
void set(T t);
}
class FooImpl implements Foo {
private Str
