Repository navigation
London | 26-JUL-SDC |Ping Wang | Sprint 2 |Improve precomputing CYF-1183 #233
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
Open
pathywang
wants to merge
2
commits into
CodeYourFuture:main
Choose a base branch
from
pathywang:improve-precomputing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use complexity to explain how the new implementation is better than the original implementation?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks of course. The original implementation compares every possible pair of strings, resulting in O(n²) pair comparisons. The updated implementation sorts the strings and compares only adjacent pairs, reducing the number of prefix comparisons to O(n). Sorting takes O(n log n) comparisons, so the overall time complexity is O(n log n + n × m), where n is the number of strings and m is the maximum string length. It also avoids repeatedly creating list slices, reducing unnecessary memory allocations. Is it OK?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If string length,$m$ , is to be taken into consideration, how does $m$ affect the complexity in the original implementation and the complexity of sorting?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. The maximum string length, m, affects the cost of comparing strings because finding their common prefix can take O(m) time in the worst case. In the original implementation, there are O(n²) pairs to compare, so the overall time complexity is O(n² × m). In the updated implementation, sorting n strings takes O(n × m × log n) in the worst case because each string comparison can take O(m). Comparing adjacent strings afterwards takes O(n × m). Therefore, the overall worst-case time complexity of the updated implementation is O(n × m × log n), which is an improvement over O(n² × m). Both implementations depend on the string length m, but your new implementation reduces the number of string comparisons from quadratic growth to sorting-level growth. So I think the complexity of sorting is better compared with the original implementation