Skip to content

Locking: move lock funcs to own package#1723

Merged
sinbad merged 4 commits into
locking-masterfrom
locking-wip/package
Nov 30, 2016
Merged

Locking: move lock funcs to own package#1723
sinbad merged 4 commits into
locking-masterfrom
locking-wip/package

Conversation

@sinbad

@sinbad sinbad commented Nov 28, 2016

Copy link
Copy Markdown
Contributor

Re-implementation of #1625. Based on PR feedback (except config changes which are still pending). Channel wrappers are gone & so is much of complexity, simpler for clients (and added local Lock struct so remove dependency on api.Lock).

Merge target is locking-master to denote that this isn't a finished API yet but to enable reviewing in bite-size chunks.

@technoweenie technoweenie left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm approving this on the condition that the locking exports are changed as suggested (#1625 (comment)) in a future PR. Since it's going to locking-master, it should unblock you until you're ready to merge to master.

@sinbad

sinbad commented Nov 30, 2016

Copy link
Copy Markdown
Contributor Author

I'm approving this on the condition that the locking exports are changed as suggested (#1625 (comment)) in a future PR

Yeah, I think that's going to need a bigger refactor of other code's use of Configuration to do properly so wanted to come back to that. Using locking-master as an intermediate step will keep this sane for everyone I hope.

@sinbad sinbad merged commit 2f7a069 into locking-master Nov 30, 2016
@sinbad sinbad deleted the locking-wip/package branch November 30, 2016 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants