Skip to content
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

Clarify that clip() behavior is undefined when min or max is outside the bounds of x #814

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

asmeurer
Copy link
Member

As discussed in today's consortium meeting.

See the discussion at numpy/numpy#24976.

…the bounds of x

As discussed in today's consortium meeting.

See the discussion at numpy/numpy#24976.
@kgryte
Copy link
Contributor

kgryte commented Sep 19, 2024

@asmeurer You opened this PR, but, based on your comments in numpy/numpy#24976 (comment), it is not clear whether you still support making this change. Are you okay with this PR moving forward, assuming that the current standardized behavior remains the same (i.e., no type promotion)?

@kgryte kgryte added this to the v2024 milestone Sep 19, 2024
@kgryte kgryte added Narrative Content Narrative documentation content. topic: Type Promotion Type promotion. Needs Discussion Needs further discussion. labels Sep 19, 2024
@asmeurer
Copy link
Member Author

Yes, I think this text is especially important given that there is no promotion. If there were promotion this text would serve no purpose, because x would just promote to the common data type and there would be no "out-of-bounds" values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Narrative Content Narrative documentation content. Needs Discussion Needs further discussion. topic: Type Promotion Type promotion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants