On Mon, Jan 8, 2018 at 10:34 PM, Nick Coghlan <ncoghlan@gmail.com> wrote

It could be useful to include a recipe in the documentation that shows a generator with suitable error handling (taking the generic connection errors and adapting them to app specific ones) while also showing how to adapt the connection to the iterator protocol, though.

Agreed +1.

This would be great for three reasons:

Error handling should be as close to the source of errors as possible (i.e.: in the iterator).
Converting error's and adapting them is a great idea;
Mostly: Any documentation that shows people how to do better error handling, is always welcome.