Bob Nystrom

> So, lack of this feature is causing entire files, with lots of other code that could benefit from the standardization of Dart formatting, to completely be hand-formatted because of...

> Please see the closed captioning 608 character set table I added. Your example was what I was referring to when I said #139 would probably fix it. I have...

> I don't see Dart ever heading in that strictness direction, so I don't think the comparison to gofmt is completely apt. Is the strictness of #golang an actual goal...

Casting a resurrection spell! After many many discussions over the years, and recent aspirations to get the Flutter repositories using `dart format` and the upcoming style (#1253), I'm persuaded that...

> The current convention is to put trailing `//` on a line to trigger as much of a disabling of the formatter as it currently allows Actually, any line comment...

> > any line comment will trigger this behavior, not just an empty one. > > Sure, but the convention people use is to just have an empty comment. (I'm...

> Maybe it would be useful to look at concrete examples of places where we'd disable the formatter currently, and see what it would look like with your proposed syntaxes?...

> A lot of the examples I've run into in Flutter code where I want to temporarily disable formatting are even shorter (e.g. just if statement expressions that run across...

This is now implemented using `// dart format off` and `// dart format on` comments. It's only supported under the new tall style (and I have no intention to implement...

> The value of my code working is infinitely higher than anything the formatter can give me. :-) Heh, fair. :)