Skip to content
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

[Lang] Raise an error for the semantic change of transpose() #6813

Merged
merged 3 commits into from
Dec 6, 2022

Conversation

strongoier
Copy link
Contributor

Issue: #5819

Brief Summary

The background is that we would like to clearly distinguish vectors from matrices. After #6528, transpose() of a vector makes no sense so we'd better raise an error and guide users towards the current practice (outer_product()).

@netlify
Copy link

netlify bot commented Dec 6, 2022

Deploy Preview for docsite-preview ready!

Name Link
🔨 Latest commit 90e6908
🔍 Latest deploy log https://app.netlify.com/sites/docsite-preview/deploys/638efc169b84cc00093118c1
😎 Deploy Preview https://deploy-preview-6813--docsite-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@strongoier strongoier merged commit 6669241 into taichi-dev:master Dec 6, 2022
@strongoier strongoier deleted the transpose branch December 6, 2022 11:58
quadpixels pushed a commit to quadpixels/taichi that referenced this pull request May 13, 2023
…dev#6813)

Issue: taichi-dev#5819

### Brief Summary

The background is that we would like to clearly distinguish vectors from
matrices. After taichi-dev#6528, `transpose()` of a vector makes no sense so we'd
better raise an error and guide users towards the current practice
(`outer_product()`).

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants