frog await: allow errors after the await within try-catch blocks.

corelib/src/implementation/future_implementation.dart

 // Copyright 2011 Google Inc. All Rights Reserved.
 // Dart core library.
 
 /**
  * Thrown if client tries to obtain value or exception
  * before a future has completed.
  */
 class FutureNotCompleteException implements Exception {
   FutureNotCompleteException() {}
   String toString() => "Exception: future has not been completed";
@@ skipping 82 matching lines @@
   void handleException(void onException(Object exception)) {
     _exceptionHandlers.add(onException);
   }
 
   void _complete() {
     _isComplete = true;
     if (_exception !== null) {
       for (Function handler in _exceptionHandlers) {
         if (handler(_exception)) {
           _exceptionHandled = true;
+          break;

[Siggi Cherem (dart-lang), 2011/12/28 20:11:59]

Matt - Something I wanted to make sure here is this change. I am assuming that
once a handler returns true, there is no need to keep calling the others. This
resembles how try-catch blocks work.

[mattsh, 2011/12/28 20:55:57]

Yes.  This is good.

         }
       }
     }
     if (hasValue) {
       for (Function listener in _listeners) {
         listener(value);
       }
     } else {
       if (!_exceptionHandled && _listeners.length > 0) {
         throw _exception;
@@ skipping 33 matching lines @@
   }
 
   void complete(T value) {
     _futureImpl._setValue(value);
   }
 
   void completeException(var exception) {
     _futureImpl._setException(exception);
   }
 }