oneapi-src / oneapi-src/unified-runtime
Move headers files into subdirectory
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
To avoid conflicts and make things clear, put the include files in some clean directory/directories.
So an end-user will write something like:
// C
#include "oneapi/unified_runtime/ur_api.h"
// C++20
import oneapi.unified_runtime;
To bikeshed, obviously.
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
The issue does not name specific files or tests; start by locating the current public include files and their build or install entry points. Compare the existing layout with the proposed oneapi/unified_runtime/ur_api.h and C++20 module paths, then define the directory structure and verify that installed C and C++ consumers can use the new paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100