Fully document the len function#6193
Merged
Merged
Conversation
mccanne
approved these changes
Sep 7, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What's Changing
This is my attempt to more exhaustively document the
lenfunction.Why
While reviewing #6174 I noticed that
lenhas been only documented in terms of supported types (which were slightly incorrect) and then the list of examples shown was incomplete. While most of its behaviors seem intuitive, on closer inspection I sensed not all of it might be obvious to a new user.Details
I constructed this through a combination of black box testing and peeking at the code as a non-developer. Therefore a thorough double check for completeness and correctness would be appreciated.
Also, talking about "type
type" and such always feels a little funky, so input on wording is also appreciated.