-
Notifications
You must be signed in to change notification settings - Fork 53
Clarify guidance on operations having data-dependent output shapes #193
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
…add-boolean-indexing-notes
Co-authored-by: Stephan Hoyer <[email protected]>
Other operations can also wind up with unknown shapes like |
@jakirkham This PR includes guidance for |
Sorry I must have missed that |
@jakirkham No worries! 😅 |
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 have a question on the terminology. Is it common to say "array computation graphs"? I would have expected a more verbose phrasing:
- libraries that build array computation graphs -> array libraries based on (or "that build") computation graphs
but maybe it's just a nitpick...
Co-authored-by: Leo Fang <[email protected]>
@leofang Updated copy based on your suggestions. |
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 text LGTM now, and the warnings are nice to have - let's get this in. Thanks for the input everyone!
This PR supersedes gh-168 by @steff456.
In summary, this PR
Notes