Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upReduce traverseInOrder time complexity and space complexity #470
+1,390
−1,410
Conversation
…e time complexity and space complexity
codecov
bot
commented
Mar 16, 2020
Codecov Report
@@ Coverage Diff @@
## master #470 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 149 149
Lines 2612 2616 +4
Branches 434 433 -1
=========================================
+ Hits 2612 2616 +4
Continue to review full report at Codecov.
|
|
@trekhleb CC! And could you please give my some advises? |
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.
stephenkingsley commentedMar 16, 2020
•
edited
In this case
traverseInOrderuse Recursive Approach. We can reduce the time complexity and the space complexity by usingStack.Recursive Approach
Complexity Analysis
Iterating method using Stack
Complexity Analysis