Bob Nystrom

Ugh, another weird interaction between trailing commas and other formatting rules. :-/

The [forthcoming](https://github.com/dart-lang/dart_style/issues/1403) [tall style](https://github.com/dart-lang/dart_style/issues/1253) does the right thing and yields the same indentation for all three calls: ```dart f() { a.b().m( t: '', // comment to force split ); a.b.m(...

@Hixie, what output would you expect here? I don't have any intuition for how Flutter-style block formatting should interact with `=>`.

The first example has a multi-line `=>` body, though. How would you format that?

> by turning it into a block with a return statement. I guess maybe I'm not being clear enough. If you were an automated formatter that was *only able to...

So should I just close this bug then? I don't know how to take action on it.

There are definitely many many multi-line `=>` member bodies. As far as I can tell, most users are happy with the output, but most of the code I see does...

OK. Having dartfmt automatically switch between `=>` and `{ return ... }` at this point would be a very large, disruptive change. It may also be a change that the...

> An impactful change, one might say. If the magnitude is large, all the more important to make sure the sign bit is actually positive.

The [forthcoming](https://github.com/dart-lang/dart_style/issues/1403) [tall style](https://github.com/dart-lang/dart_style/issues/1253) produces the desired output in both of these examples now: ```dart class C { static HandlerResponse handleRouteReplaced( ReplaceRoute action, RouteState state, ) => HandlerResponse.updateOnly( state.copy(active: action.route,...