Java/TypeChecking: Difference between revisions
From charlesreid1
(Created page with "This gets complicated fast when you're using generic types. See https://charlesreid1.com:3000/cs/java/src/master/hash/README.md#timing-comparison-built-in-map-vs-hand-rolled-...") |
No edit summary |
||
| Line 6: | Line 6: | ||
[https://stackoverflow.com/questions/27153731/parametrized-method-in-java-try-catch-does-not-catch-classcastexception-on-and/27154147#27154147 This stack overflow question] addresses some similar issues. | [https://stackoverflow.com/questions/27153731/parametrized-method-in-java-try-catch-does-not-catch-classcastexception-on-and/27154147#27154147 This stack overflow question] addresses some similar issues. | ||
The approach that introduces the least amount of conflict is to use (Object o) as a parameter type, then cast to whatever type you need. If you must cast to a type that takes generic parameter types, like a Map or a Set, you can explicitly tell the complier not to complain by adding the decorator <code>@SuppressWarnings("unchecked")</code>. See [https://stackoverflow.com/questions/509076/how-do-i-address-unchecked-cast-warnings#509115 this stack overflow question] for some additional information. | |||
Revision as of 01:58, 29 June 2017
This gets complicated fast when you're using generic types.
Neal Grafter's blog has a page talking about reified generics. This has to do with casting objects to generic types, and casting to objects that utilize the diamond notation, like Collections objects.
This stack overflow question addresses some similar issues.
The approach that introduces the least amount of conflict is to use (Object o) as a parameter type, then cast to whatever type you need. If you must cast to a type that takes generic parameter types, like a Map or a Set, you can explicitly tell the complier not to complain by adding the decorator @SuppressWarnings("unchecked"). See this stack overflow question for some additional information.