exercises(matching-brackets): example: avoid using allocator #338
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
The user is allowed to add conditions like this to the doc comment of a tested function.
Add the closing character to the stack, not the opening one. This makes the body of the helper function look more natural, and reduces the complexity of the longer line in isBalanced.
booniepepper
approved these changes
Oct 4, 2023
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.
The user is allowed to add their own reasonable conditions to the contract of a tested function. Illustrate one way to avoid using the allocator.
Also, demonstrate adding the closing character to the stack, not the opening one. This makes the body of the helper function look more natural, and slightly reduces the complexity of the longer line in
isBalanced.Refs: #313
To-do:
stacktobuf.falseif nesting depth exceeds 100.