Remove the line number and file information from *all* folded frames.

README.md

 This library provides the ability to parse, inspect, and manipulate stack traces
 produced by the underlying Dart implementation. It also provides functions to
 produce string representations of stack traces in a more readable format than
 the native [StackTrace] implementation.
 
 `Trace`s can be parsed from native [StackTrace]s using `Trace.from`, or captured
 using `Trace.current`. Native [StackTrace]s can also be directly converted to
 human-readable strings using `Trace.format`.
 
 [StackTrace]: http://api.dartlang.org/docs/releases/latest/dart_core/StackTrace.html
@@ skipping 36 matching lines @@
 together multiple stack frames from the Dart core libraries, so that only the
 core library method that was directly called from user code is visible. For
 example:
 
     dart:core                                   Object.noSuchMethod
     pkg/stack_trace/lib/src/trace.dart 47:21    Trace.terse.<fn>
     dart:core                                   List.reduce
     pkg/stack_trace/lib/src/trace.dart 40:35    Trace.terse
     pkg/stack_trace/lib/stack_trace.dart 24:28  format
     test.dart 21:29                             main.<fn>
-    dart:async                                  Timer.Timer.<fn>
 
 ## Stack Chains
 
 This library also provides the ability to capture "stack chains" with the
 `Chain` class. When writing asynchronous code, a single stack trace isn't very
 useful, since the call stack is unwound every time something async happens. A
 stack chain tracks stack traces through asynchronous calls, so that you can see
 the full path from `main` down to the error.
 
 To use stack chains, just wrap the code that you want to track in
@@ skipping 119 matching lines @@
 
 That's a lot of text! If you look closely, though, you can see that `main` is
 listed in the first trace in the chain.
 
 Thankfully, you can call `Chain.terse` just like `Trace.terse` to get rid of all
 the frames you don't care about. The terse version of the stack chain above is
 this:
 
     test.dart 17:3   runAsync
     test.dart 13:28  scheduleAsync.<fn>
-    dart:isolate     _RawReceivePortImpl._handleMessage
     ===== asynchronous gap ===========================
-    dart:async                                _Future.then
-    test.dart 13:12                           scheduleAsync
-    test.dart 7:18                            main.<fn>
-    package:stack_trace/src/chain.dart 93:20  Chain.capture
-    test.dart 6:16                            main
-    dart:isolate                              _RawReceivePortImpl._handleMessage
+    dart:async           _Future.then
+    test.dart 13:12      scheduleAsync
+    test.dart 7:18       main.<fn>
+    package:stack_trace  Chain.capture
+    test.dart 6:16       main
 
 That's a lot easier to understand!
 
 [Zone]: https://api.dartlang.org/apidocs/channels/stable/#dart-async.Zone