oneapi-src / oneapi-src/level-zero
Image API intentionally not backwards compatible?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Description
From https://spec.oneapi.com/versions/0.7/oneL0/core/PROG.html#images:
This methodology allows for device-specific encoding of image contents (e.g., tile swizzle patterns, lossless compression, etc.) and avoids exposing these details in the API in a backwards compatible fashion.
Is that wording intentional? I would assume backwards compatibility for the Image API is a desired quality , not something to avoid...
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
Start with the linked oneAPI 0.7 PROG.html Images section and review the sentence about device-specific image encoding and backwards compatibility. Confirm the intended meaning with a maintainer, then update the specification wording if it is incorrect. Done means the statement clearly reflects the supported compatibility policy.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100