This is necessary because the assertion failing is "compiles without warnings".  This generates a warning, so yes, in terms of that test, it is a failure.  I toyed with expanding the function to permit "compiles-with-certain-warnings" but it was just easier to suppress this by claiming it.

Users' code won't need to jump through this hoop, but users' builds may show that warning in their build log.  I dug into the compiler impl, and there are some "built in" annotations it special cases... this isn't one of them.  the only reason this is necessary is because of the nature of the assert method in this test, that it claims that compilation occurs without warnings for generics.