Repository navigation
Add a page detailing the time complexity of operations on built-in types #154363
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
Merged
StanFromIreland
merged 18 commits into
python:main
from
StanFromIreland:timecomplexity-doc
Aug 24, 2026
Merged
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
80088bf
Add a 'Time complexity of operations on built-in types' section
StanFromIreland 84b95f9
Ned's suggestion for blog post rec.
StanFromIreland 1982202
Revert that
StanFromIreland 64fb553
Little fixups
StanFromIreland 0392d7e
Apply review suggestions from Pieter and Bénédikt
StanFromIreland 9e1a82a
Address Pieter's very helpful review
StanFromIreland f19c249
Merge branch 'main' into timecomplexity-doc
StanFromIreland d0ca44c
Simplify complexity notation addressing part of Serhiy's comments
StanFromIreland 7e297d6
Carol's suggestion
StanFromIreland 22d5586
Ned's review
StanFromIreland 5f21510
Missed a few, oops!
StanFromIreland 29e2017
Ned's review
StanFromIreland 4d223f1
Address @dg-pb's review re. reverse string search complexity
StanFromIreland a893080
Try to simplify footnote
StanFromIreland c4a75fd
Remove note
StanFromIreland eac04b8
Drop "very"
StanFromIreland 27e9cd6
Address Bénédikt's review
StanFromIreland 116f21e
Switch back to `l`
StanFromIreland 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
Prev
Previous commit
Switch back to
l
- Loading branch information
commit 116f21ec9f82125eeaa19453544e43bdd4716eb9
Some comments aren't visible on the classic Files Changed page.
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
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.
This may seem silly, but I would suggest using
Linstead ofl. Even with monospace fonts, it may not necessarily be readable for everyone.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.
I can see people confusing it with
I, but I don't think that's a big issue here. It would however be inconsistent with the other tables, which would bug me.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.
Considering we are using
l[i:j], I still think it's better to haveL. It's not an issue to use another capitalization with other tables here. What matters is readability for me. Or you can usevfor "vector".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.
Merge the
listandtuplesections and uses, as in the main documentation.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.
For context, it was
soriginally in this PR and later changed at Ned's request. I've updated toL, I don't think merging is correct. Unlike the main docs, this is more of a reference.