-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Enhanced RDoc for Struct #4890
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
Enhanced RDoc for Struct #4890
Conversation
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 for working on this. Only a few requests for changes.
* struct[member] -> object | ||
* struct[index] -> object | ||
* struct[name] -> object | ||
* struct[n] -> object |
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 would use a single line with key
instead of name
and n
. From a caller's perspective, the two lines are the same. Same change for []=
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.
These two forms seem different to me.
More importantly, replacing name and n with key would force some clumsiness into the discussion:
- +key+th or something perhaps worse.
- Raises NameError if +key+ is not an integer or a member name.
- Raises IndexError if +key+ is an integer that is out of range.
I'd prefer to leave stet.
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.
Since this is just a preference on my part, I'm fine leaving as-is.
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.
Looks good!
Treated: