Use correct first bucket during grow
#28
Merged
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.
Fixes a regression caused by using the wrong next bucket in #27 Confirmed to work with iced's
tour
example.I think this is correct but it would be helpful if anyone could double check the
first_bucket
logic here.Also updated the
grow_horizontally
example to avoid the allocation failing after resize because of shelf height. I'd like to double check that this expectation change is ok with @hecrj before merging.