Skip to content

MAINT: result_type cosmetic refactor #142

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

Merged
merged 1 commit into from
Apr 2, 2025

Conversation

crusaderky
Copy link
Contributor

No description provided.

@crusaderky crusaderky force-pushed the result_type_nits branch 2 times, most recently from 56a2aa7 to 788e6be Compare April 2, 2025 10:41

if len(B) == 0:
if not dtypes:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This got me off at a first glance, but yeah it's OK because dtypes contains both arrays and dtypes.
Is fine, even if resembles a bit a snippet I recently saw in somebody's going through the "intro to python" online course: mytuple = [].

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dtypes list contains exclusively dtypes though.

@ev-br ev-br merged commit d13ab1b into data-apis:main Apr 2, 2025
19 checks passed
@ev-br ev-br added this to the 2.4 milestone Apr 2, 2025
@crusaderky crusaderky deleted the result_type_nits branch April 2, 2025 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants