Eclipse always warns for a naked use of Class. So, Eclipse thinks, more or less, that any time you might want to say X<Class>, that you really meant to say X<Class<?>>, or X<Class<something>>, which is in some cases the same sort of beast. However, this is not one of those cases. I think that an @SuppressWarnings is called for.
On Fri, May 29, 2009 at 8:51 AM, Sean Owen <sro...@gmail.com> wrote: > I don't think so... that class doesn't need a new parameter. It is an > AbstractParameter, parameterized by Class, already. > > Actually, I opened this up again in IntelliJ and no longer see the > unchecked-cast sort of warnings I remember on this code. I certainly > recall something like that here. > > What's the error you're getting again? > > On Fri, May 29, 2009 at 1:33 PM, Benson Margulies <bimargul...@gmail.com> > wrote: > > Should that class really be ClassParameter<T> instead of just > > ClassParameter? >
