Refactor non-standard literal construction (#1443)
Fix problem with the contiguous operator constructing non-standard shape literals. A non-standard literal will almost never be used, since a literal is known at compile time. Added some comments on the intended behavior:
- literal{shape, vector} constructor with a non-standard shape is intended to keep the same ordering as the given vector. The data buffer will be populated such that when the non-standard indexing is used the original order is as given.
- literal{shape, argument} constructor directly copies the data buffer from the argument
- Changed non-standard literal fill() to use tensor_view iterators as it handles non-standard shapes now
- Changed the contiguous ref_ops_test to be more helpful
Showing
Please register or sign in to comment