Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
blueprint-core-1.6.2
-
None
Description
Blueprint should only check constuctor and method arguments depending on their class the way the JVM works at runtime.
At runtime there is no difference between:
setSomething(List);
and
setSomething(List<String>);
Furthermore Java prevents having both methods above declared in the same class (same applies if List were List<Object>). A List is a List no matter the generic type. The generic type checking is made at compilation time. Blueprint is not a compiler
Please add a flag to enforce or not the generic type checking!
Attachments
Issue Links
- is related to
-
ARIES-960 Support type inference and generics
- Resolved