Skip to content

Resolve issue #41 #42

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

Merged
merged 1 commit into from
Dec 10, 2017
Merged

Resolve issue #41 #42

merged 1 commit into from
Dec 10, 2017

Conversation

escalonn
Copy link
Contributor

Resolves #41 by preventing Node.pop_greatest_child from creating a node with its own children.

@escalonn
Copy link
Contributor Author

This is probably safe because when I tried uncommenting the asserts on lines 381-382 (before making the change in this commit), no tests failed, implying that Node.pop_greatest_child always creates childless nodes in the tests.

@escalonn
Copy link
Contributor Author

(The build is only failing because of the issue between coverage 4.0 and Python 3.2.)

@escalonn escalonn mentioned this pull request Mar 13, 2017
@escalonn escalonn mentioned this pull request Dec 2, 2017
@chaimleib chaimleib changed the base branch from master to dev December 10, 2017 19:52
@chaimleib
Copy link
Owner

chaimleib commented Dec 10, 2017

Thanks! That was a really gnarly one!

@chaimleib chaimleib merged commit 234ecff into chaimleib:dev Dec 10, 2017
@escalonn escalonn deleted the issue41 branch December 11, 2017 01:36
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