oneapi-src / oneapi-src/unified-runtime
Define a policy for adding adapter specific functionality
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
We should define a policy for when we will accept additions to unified runtime and when we will not accept a change and recommend that the caller would use native_handle interop instead.
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the unified runtime's adapter-specific functionality and the existing native_handle interop guidance. Determine the criteria for accepting adapter-specific additions versus directing callers to native_handle. Done means the policy and its decision boundary are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100