We still need the error handler because the default child-translator error handler fails translation on the parent, no matter whether or not the error was caught. (Another result of our fake-async control flow... But I'm not sure there's anything we can do to fix it globally that won't break old translators.)
We still need the
errorhandler because the default child-translatorerrorhandler fails translation on the parent, no matter whether or not the error was caught. (Another result of our fake-async control flow... But I'm not sure there's anything we can do to fix it globally that won't break old translators.)Addresses #3311