You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently ti.Vector is implemented as ti.Matrix with m=1. However, this makes code in other parts unable to distinguish between a vector and an actual matrix with m=1, which causes some ad-hoc checks and parameters when number of dimensions matters. For example, we need to manually specify whether to treat m=1 as an actual dimension when transferring to/from external arrays. To get rid of these, we need to separate ti.Vector and ti.Matrix into two classes.
The text was updated successfully, but these errors were encountered:
strongoier
changed the title
Separate ti.Vector and ti.Matrix implementations
[Lang] [refactor] Separate ti.Vector and ti.Matrix implementations
Aug 17, 2021
Currently
ti.Vector
is implemented asti.Matrix
withm=1
. However, this makes code in other parts unable to distinguish between a vector and an actual matrix withm=1
, which causes some ad-hoc checks and parameters when number of dimensions matters. For example, we need to manually specify whether to treatm=1
as an actual dimension when transferring to/from external arrays. To get rid of these, we need to separate ti.Vector and ti.Matrix into two classes.The text was updated successfully, but these errors were encountered: