Added support for no timeout locks on db files #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request has been added to boltdb/bolt (#494) but has been queued for processing.
So I submit it there in the hope that it can be merged into a reasonably maintained repo so I dont have anymore to maintain a separate repo on the side.
Beside my application needs, I think this change is beneficial to the community as it completes the timeout locking API which didn't support an obvious case (failing right away if the database lock file can not be acquired instead of having to wait a given duration). I took the opportunity to refactor slightly these few lines of code to make them cleaner.
Full discussion of the initial boltdb/bolt pull request is there:
boltdb/bolt#494