-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
DOC: Make input/output type consistent and add more examples for documentation #23611
Conversation
Wonder if anyone knows how to fix the failed tests related to old_gcc and armv7_simd_test? Thanks in advance! |
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.
There's no need for the updated parameter descriptions, array_like
encompasses scalars.
Got it! Thanks for the explanation. It looks like sometimes the input type uses "array_like" but output type uses "ndarray or scalar", I think that's what caused the confusion. I can update to make them consistent! |
[skip cirrus] [skip azp] [skip actions]
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.
The examples in which the output is a scalar LGTM. I'll go ahead and merge if CI looks good. Thanks @Sarah-Yifei-Wang.
[skip actions] [skip azp] [skip cirrus]
[skip azp] [skip actions] [skip cirrus]
I noticed in quite a few scimath function, the input type is array_like, but output type is ndarray or scalar. Initially this caused some confusion for me, making me feel input does not contain scale. To avoid future confusion, this PR is to: