Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify the Nexter interface #93

Merged
merged 4 commits into from
Aug 7, 2014
Merged

Conversation

kortschak
Copy link
Contributor

Refer to issue #92 for discussion.

Because of the necessary association between graph.Next(it) and it.Result() calls, this PR should be reviewed carefully - during the changes I found a number of times where I had missed/altered the it. These were caught by tests, but I don't guarantee there are not others that tests miss.

This change allows a Nexter to be used in the same manner as a scanner
using a for graph.Next(it) {} construction.

It is important that graph.Next(it) and any associated it.Result() calls
operate on the same iterator.
@kortschak
Copy link
Contributor Author

I've had a careful and time detached review and I am confident that this is all OK.

Conflicts:
	graph/leveldb/all_iterator.go
	graph/leveldb/iterator.go
	graph/memstore/triplestore.go
	query/gremlin/finals.go
@kortschak
Copy link
Contributor Author

PTAL

barakmich added a commit that referenced this pull request Aug 7, 2014
Simplify the Nexter interface
@barakmich barakmich merged commit 7cd740a into cayleygraph:master Aug 7, 2014
@kortschak kortschak deleted the nexter branch August 7, 2014 05:37
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