[bug] [lang] Fix copyback for fortran contiguous numpy arrays #6376
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #6305
Taichi kernel assumes input external array are row major / c_contiguous for now so this PR throws an error message when the input numpy array isn't contiguous.
Note that we only supports inplace update for c_contiguous numpy arrays but for historical reason support for f_contiguous array was added via copying (
ascontiguousarray()
) as well, thus this PR tries to preserve the support to avoid breaking old code.Also the support for f_contiguous numpy array was halfly done since
ascontiguousarray()
may return a new numpy array, Taichi kernels just read/write on the copied array and don't copy the values back to the original numpy array.This PR fixes the bug mentioned above by adding a callback function to copy values back, although copying behavior isn't efficient it guarantees correctness so that we can improve it in the future.
Issue: #
Brief Summary