non-ideal split for nested calls, generic types in arg lists

[jmesserly]

not a big deal, but here's an example where formatting should maybe do something different?

example:

bool doStuff(String firstArgX, {String secondArg, String arg3foo, Map<String,
    String> anotherArg, bool yetAnotherArg: false, bool tooManyArgs: true}) {

I renamed the names from my code, but I think I preserved the length to reproduce :)

ideally it would prefer to split before Map<String, String> instead of splitting the generic type.

[jmesserly]

the idea would sort of be to respect nesting. Hmmm, maybe this case is similar:

foo(a0, a1, bar(a2_0, a2_1, a2_3), a3, a4, ...)

if possible would be nice if the bar(...) call is kept together. Not sure if it works like that for functions (did not try yet)

[jmesserly]

Another example was a split here:

/*... code here ...*/ {bool useColors: true, void
    printFn(obj)}

[jmesserly]

another comment along the same lines:

When breaking arguments, nested expressions should have a penalty for breaking again. That is:
foo(gee(), bar(x, y)) should not be broken as

foo(gee(), bar(x,
  y))

but rather:

foo(gee(),
       bar(x, y))

Same for longer expressions like x?y:z, or even just o.x.