Bob Nystrom

> Have you considered requiring leaving operators on the previous line to explicitly indicate that the expression wraps to the next line? Yes, this is what dartfmt always does. In...

> I actually meant use this rule for all operators, including the dot invocation operator I think that would cause mass rioting in the streets. > I think this would...

> What do you think would be the primary objection that would cause riots? There are literally millions of method chains in existing Dart code where the `.` is on...

> There is nothing special about "child" or "children"; not all widgets use those names, e.g. MaterialApp (the first widget people come across) uses "home", while Scaffold and AppBar (the...

> This likely means that in developers' minds child widgets are conceptually separate from "properties", so they put them last. Yes! One of the reasons I was interested in exploring...

I did toy with a syntax similar to what you have here, and also played around with something like: ```dart Scaffold { body: Home { ... } persistentFooterButtons: FlatButton {...

> Right. We already use { } for all kinds of things: classes, maps, named parameters, methods, functions, switch statements, etc. This just continues the trend. That's true, but in...

Leaving this here as a data point: https://devrant.com/rants/1897404/i-really-do-like-flutter-dart-but-i-just-cannot-be-the-only-who-thinks-that-the

There's a lot to reply to here. :) First, I think we should distinguish between control flow in argument lists and in collection literals. The two contexts are pretty different....

I should have been clearer but in that section I was also assuming that `children` had been turned into a rest parameter so that those child widgets get passed positionally....