This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author adelfino
Recipients adelfino, ammar2, benjamin.peterson, docs@python, methane
Date 2018-06-17.15:57:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529251021.03.0.56676864532.issue33872@psf.upfronthosting.co.za>
In-reply-to
Content
IMHO, if we deem it useful for users not to expect the time complexity of a linked list for list elements access to the extent of adding a comment in the glossary, there's no reason it isn't useful to someone who is reading the actual list definition. Moreover, I don't see the reason why someone would read the list glossary entry after reading the list definition.

I believe glossary entries should be a (rather small) subset of the topics they touch.

All of this, of course, if Ammar is not right about list not requiring O(1) time complexity.

Please note that, while interesting, I'm not proposing to document the time complexity in list definition per se, but only because it's already documented in the glossary.
History
Date User Action Args
2018-06-17 15:57:01adelfinosetrecipients: + adelfino, benjamin.peterson, methane, docs@python, ammar2
2018-06-17 15:57:01adelfinosetmessageid: <1529251021.03.0.56676864532.issue33872@psf.upfronthosting.co.za>
2018-06-17 15:57:01adelfinolinkissue33872 messages
2018-06-17 15:57:00adelfinocreate