-
Notifications
You must be signed in to change notification settings - Fork 16
Implement checks on new array types to prevent developer mishaps #371
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
Conversation
f1a334d to
1d1fb5b
Compare
inducer
left a comment
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! A few follow-ups below, otherwise LGTM!
pytato/array.py
Outdated
| _mapper_method: ClassVar[str] = "map_data_wrapper" | ||
|
|
||
| def __post_init__(self) -> None: | ||
| pass |
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.
- Add a comment to explain?
- This somehow feels quite broad, in that it assumes that the checks are the only thing happening in
__post_init__? This might make more sense if the checks were in a sub-method which could then be selectively neutered? I'm not insisting on this, FWIW, merely raising the question.
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.
Added the comment, thanks!
1d1fb5b to
8908a98
Compare
|
Thanks! |
8908a98 to
321d293
Compare
See the discussion in #365.