-
Notifications
You must be signed in to change notification settings - Fork 16
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
Better slicing #1059
Better slicing #1059
Conversation
(HostPlacement, (Shape) -> Shape => [concrete] Self::logical_host_shape), | ||
(HostPlacement, (Tensor) -> Tensor => [concrete] Self::logical_host_kernel), |
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.
nit
: we often put the the logical kernel at the top for each placement (e.g identity)
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 was thinking about this and how we should sort kernel types, I thought it would be good if we sort them by kernel types (whether they're runtime / replicated protocols / lowering) and then we sort everything alphabetically after the input types, something similar as @jvmncs did in a previous PR. I couldn't find something better for now.
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.
Nice! Good work @rdragos !
Closes #1064
Does a few things:
BitArray
. See BitArray slicing #1066ConstantOp
.