Smarter wrapping logic for long parameter lists

[Egorand]

Fixes #274

[Egorand]

Not sure what the style guide says about that, but having nested wrapping felt like an overkill. Hence, lambda types as function parameters are always single-line, even if they wrap.

[Egorand]

This behavior should also be consistent with the discussion on #256: we don't wrap the lambda parameters, but we do wrap the function parameters.

[Egorand]

I think I'll update this PR to cover #291 as well. Any feedback here so far?

[JakeWharton]

I certainly like the results. When do you emit a parameter spec with wrapping=False?

[Egorand]

When you've got a parameterized LambdaTypeName as the type of the param:

fun veryLongFunctionName(
        veryLongParameterName: (java.io.Serializable, java.lang.Appendable, kotlin.Cloneable) -> kotlin.Unit,
        i: kotlin.Int
) = kotlin.Unit

[JakeWharton]

Ah, nice. I think I'd prefer if we flipped the boolean so that it wraps by default and we opt-out only in the lambda special case.

[Egorand]

Can do

[Egorand]

Fixes #291

[gilgoldzweig]

Any updates on this request?

[Egorand]

@gilgoldzweig we'll most likely go with a solution for #532, which should handle this use-case as well.

[gilgoldzweig]

Cool, is there any way to make it work now?

[Egorand]

There's no workaround unfortunately, but if your function/constructor has more than 2 parameters we'll auto-wrap it.