-
Notifications
You must be signed in to change notification settings - Fork 89
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
fix: make from_iter
require iterables!
#2353
Conversation
Codecov Report
Additional details and impacted files
|
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.
Just comments for now because I'm a little wary of this one. I get that you're trying to make the function name more literal, and therefore more guessable without recourse to the documentation. I'm hesitant because there might be some things people expect would work, even though they're not literally iterables.
If the tests pass, then if there are any such cases, they're not explicitly being tested.
e23ff71
to
8c48428
Compare
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 see that the PR is only about rejecting non-iterables, and you can merge when ready.
Should I turn the problem with broadcasting strings into an issue?
Although
from_iter
can understand non-iterables, I think we really want to restrict it to only returning layouts/arrays.