Fix the weird names that can occur in exceptions and logs when there is no

lib/unittest/interfaces.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 // To decouple the reporting of errors, and allow for extensibility of
 // matchers, we make use of some interfaces.
 
 /**
  * The ErrorFormatter type is used for functions that
  * can be used to build up error reports upon [expect] failures.
  * There is one built-in implementation ([defaultErrorFormatter])
  * which is used by the default failure handler. If the failure handler
  * is replaced it may be desirable to replace the [stringDescription]
  * error formatter with another.
  */
 typedef String ErrorFormatter(actual, Matcher matcher, String reason);
 
 /**
  * Matchers build up their error messages by appending to
  * Description objects. This interface is implemented by
  * StringDescription. This interface is unlikely to need
  * other implementations, but could be useful to replace in
  * some cases - e.g. language conversion.
  */
 interface Description {
+  /** Change the value of the description. */
+  Description replace(String text);
+
   /** This is used to add arbitrary text to the description. */
   Description add(String text);
 
   /** This is used to add a meaningful description of a value. */
   Description addDescriptionOf(value);
 
   /**
    * This is used to add a description of an [Iterable] [list],
    * with appropriate [start] and [end] markers and inter-element [separator].
    */
@@ skipping 32 matching lines @@
 
   /**
    * This handles failures given the actual [value], the [matcher]
    * and the [reason]. It will typically use these to create a
    * detailed error message (typically using an [ErrorFormatter])
    * and then call [fail].
    */
   void failMatch(actual, Matcher matcher, String reason);
 }