-
Notifications
You must be signed in to change notification settings - Fork 62
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
Implement clone() #429
Implement clone() #429
Conversation
Fixes #342.
The failures are distributed notebook flakiness; unrelated, so marking ready for review. I didn't understand the #342 comment about not making this a symbol. Without the |
The test failures are for distributed things: |
triage review — just |
The failures are just the distributed tests failing, issue #432. This is ready for re-review / merging. |
Since we're incorrectly returning an alias, modifications to the returned tensor will show up in the original tensor. Add a test that demonstrates this, which should remind us to revisit this implementation once we properly implement functionalization. Thanks Luca Antiga for the idea. Also, it turns out PyTorch fixed an issue with their sparse_coo in the interim and so that test started passing. So this also removes the sparse test's xfail.
for more information, see https://pre-commit.ci
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.
Ship it!
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Fixes #342.
What does this PR do?
Fixes #342
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Always ;-)