I agree with the proposal.

The reason we trigger the error after we stop, is to give the client a chance to start again on failure:
```javascript
poller.on('error', _.bind(poller.start, poller));
```
Which actually, solves the `ignoreErrors` issue with one line and could be an alternative implementation.

Either way, if we opt in for ignoring errors by default, we want the event to trigger before we proceed, to give the client the option to halt on errors.

Thinking out load, I am not sure if we need this in the library level per say, but I don't have any strong objections, mostly the motivation is trying to keep this helper as lean and generic as possible, and in this case, this doesn't seem to add a lot of extra fat.

Either way, the proposal looks good