[BUG] Maintain storage and descriptor types across views
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 127
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 11
Description
Currently when a view is created from a tensor, or when temporary tensors are created, they aren't necessarily using the same types of storage and descriptors as the original tensors. This only shows up when using the advanced API where custom storage is used, but it should be uniform across the entire API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by tracing view creation and temporary tensor construction through the advanced API, then compare their storage and descriptor types with the source tensor; done means custom-storage cases preserve those types consistently across the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100