19 lines
728 B
Plaintext
19 lines
728 B
Plaintext
|
=== On 2015-01-20T15:41:40Z Ann Campbell Wrote:
|
||
|
|
\[~nicolas.peru], you're going to have to help me out with the whys and wherefores on this one.
|
||
|
|
|
||
|
|
=== On 2015-01-20T16:00:01Z Freddy Mallet Wrote:
|
||
|
|
This rule seems to duplicate RSPEC-107 ???
|
||
|
|
|
||
|
|
=== On 2015-01-21T17:39:38Z Nicolas Peru Wrote:
|
||
|
|
\[~freddy.mallet] This is about Type parameters not parameters.
|
||
|
|
|
||
|
|
\[~ann.campbell.2][~freddy.mallet] For me this is the same reasons as for RSPEC-107 : if you have too many type parameters then your class/method is probably doing too many things.
|
||
|
|
|
||
|
|
Another reason to avoid too many type params is readability :
|
||
|
|
|
||
|
|
----
|
||
|
|
<S, T, U, V> void foo() {} //not really readable
|
||
|
|
<String, Integer, Object, String>foo(); // especially on invocations
|
||
|
|
----
|
||
|
|
|