Lines Matching refs:handleErrors
641 handleErrors(
650 The ``handleErrors`` function takes an error as its first argument, followed by
653 ``handleErrors`` function will visit each handler in the sequence and check its
658 Since the list of handlers passed to ``handleErrors`` may not cover every error
659 type that can occur, the ``handleErrors`` function also returns an Error value
661 ``handleErrors`` does not match any of the handlers it will be returned from
662 handleErrors. Idiomatic use of ``handleErrors`` thus looks like:
667 handleErrors(
679 ``handleErrors`` except that it will terminate the program if an unhandled
684 possible, use handleErrors and propagate unknown errors up the stack instead.
688 may be a better choice than handleErrors, as it simplifies control flow when
769 Error recovery attempts may themselves fail. For that reason, ``handleErrors``
784 Any error returned from a handler will be returned from the ``handleErrors``
973 which holds a list of user defined errors. The ``handleErrors`` routine
975 order. If all contained errors can be handled, ``handleErrors`` will return
976 ``Error::success()``, otherwise ``handleErrors`` will concatenate the remaining