fix: Split bug #301
Open
fix: Split bug #301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change-set adds the final code for the sixth example from the "Learn Rust With Entirely Too Many Linked Lists" book.
Fixes a bug in the tutorial that happened when `split_before` and `split_after` resulted in an empty split. This was fixed by checking for an empty split and updating the `front` and `back` pointers accordingly. This change-set fixes both the final code and the tutorial text.
|
There are 2 commits here. One adds the final |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR creates a test cases that shows a bug with the
split_beforeandsplit_aftercode. This PR fixes the bug and updates the tutorial with details about the issue.