Fixed #7: Documented state parameter as non-empty

Note that I would not really consider this as a backwards
compatibility problem, as there is a documented way of
returning error codes, and an error code exists for this
situation. One would expect any reasonable implementation
to check for non-null as a sanity check, as it so cheap.

The exception would be if it was documented as a performance
critical method (which it is, but we don't care about
performance), where you would probably either put a blanket
warning "No pre-conditions will be checked" for the module,
or ideally on just the performance critical functions.

0 files changed, 0 insertions, 0 deletions