Brian J. Miller

I should have also included that we consider bounty based work on any of our OSS libs, if you want a defined approach and timeline.

Noted, thanks for the issue. I don't know when we'll get to this, a PR following the current code style with unit tests always speeds up the process if you...

This actually appears to be an issue with semver breakage in the specification between 1.0.0 and 1.0.1. 1.0.0 Version: > The revision property MUST NOT be used if the Statement's...

My concern with including something like this in the library is that it is blocking and could block for a _really_ long time and cause an inordinate number of requests...

The problem with that approach would be that you can't be doing work to set the global because you've been blocked.

Sure, but which, both? Ultimately these questions are all excellent, but also the reason why we just leave it up to the user to decide what works best for their...

@WillSkates interesting. With us dropping 5.4 this can be an option. Would need to be named appropriately given the above implementation, though I'd wonder does it make more sense to...

@WillSkates no, I meant yielding after each statement which should be a fairly tight loop. Batch sizing is already handled via the `limit` query string parameter which is already in...

This is unlikely to occur as the code is relatively stable and while not necessarily PSR2 it is at least consistent, and there wouldn't be any real benefit in taking...

@WillSkates oh, I know the reasons trust me, and that is a great suggestion for a non-distributed library or one with excellent test coverage, unfortunately I feel like that ship...