Disable formatting and add new-lines to make tests faster.

lib/src/codegen/dart_codegen.dart

Index: lib/src/codegen/dart_codegen.dart
diff --git a/lib/src/codegen/dart_codegen.dart b/lib/src/codegen/dart_codegen.dart
index 8b689952a5c632198ea3df1a84e4899cf5778385..0ad79bd2377cde064c42c943ab3960d4c8d6f0b5 100644
--- a/lib/src/codegen/dart_codegen.dart
+++ b/lib/src/codegen/dart_codegen.dart
@@ -67,6 +67,25 @@ class FileWriter extends java_core.PrintStringWriter {
   bool _format;
   String _path;
   FileWriter(this._format, this._path);
+  int indent = 0;
+
+  void print(x) {
+    if (_format) {
+      super.print(x);
+      return;
+    }
+
+    if (x == '{') {

[Siggi Cherem (dart-lang), 2015/02/26 21:03:49]

turns out that the ToStringVIsitor class calls print with individual symbols (;,
{, and }), so this is sufficient for the purpose of testing the output of the
core libraries.

[Leaf, 2015/02/26 21:42:14]

Won't this break things?  For example, printing a string interpolation seems to
call print with a single '}' to terminate the interpolation, but we don't want
to add a new line in the middle of the string, right?

[Jennifer Messerly, 2015/02/26 23:49:50]

yeah, +1 on changing the visitor ... IMO it shouldn't be very hard, I found
analyzer's printer code to be very straightforward. I mean worst case, you could
copy+paste it and add newlines at strategic locations. But maybe I've been
working with js_ast's Printer too much lately. :)

+      indent++;
+      x = '{\n${"  " * indent}';
+    } else if (x == ';') {
+      x = ';\n${"  " * indent}';
+    } else if (x == '}') {
+      indent--;
+      x = '}\n${"  " * indent}';
+    }
+    super.print(x);
+  }
 
   void finalize() {
     String s = toString();