Consider partitioning RAJA.hpp
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 598
- Forks
- 118
- Avg merge
- 21h 29m
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
Not a real issue, but it appears that the RAJA.hpp header file has become cluttered with a bunch of macro definitions and other things based on various CMake config variables, compiler emitted #defs, etc.
**Describe the solution you'd like**
Assess whether it would be clearer and easier to maintain if the contents of the RAJA.hpp file were broken apart into multiple simpler, more-focused headers.
**Describe alternatives you've considered**
No alternative considered.
**Additional context**
Just a thought related to code health and maintenance.
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 by reviewing RAJA.hpp and the macro definitions tied to CMake configuration variables and compiler-emitted definitions. Trace how the header is included and identify whether its contents have clear, simpler boundaries. Done means producing an agreed assessment or decomposition plan that improves clarity and maintainability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100