how to handle raw type warnings

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

how to handle raw type warnings

taher
Hi Everyone,

Right now, we have 528 warnings on trunk out of which 238 are about raw types and 118 never used imports. So we can already eliminate most of the warning quite quickly.

Before I issue a JIRA and submit patches, I would like to first know what is the standard in here with respect to generics? Do you prefer to avoid generics and just suppress warnings everywhere or do you actually want to apply them? And what should we do about code receiving mixed object types to a generic collection?

Taher Alkhateeb
Reply | Threaded
Open this post in threaded view
|

Re: how to handle raw type warnings

Jacques Le Roux
Administrator
Le 26/03/2015 06:11, Taher Alkhateeb a écrit :
> Hi Everyone,
>
> Right now, we have 528 warnings on trunk out of which 238 are about raw types and 118 never used imports. So we can already eliminate most of the warning quite quickly.
>
> Before I issue a JIRA and submit patches, I would like to first know what is the standard in here with respect to generics? Do you prefer to avoid generics and just suppress warnings everywhere or do you actually want to apply them?

We prefer to apply them, for collections have a look at UtilGenerics.java

> And what should we do about code receiving mixed object types to a generic collection?

A collection

Jacques

>
> Taher Alkhateeb
>