[DEBT] rename .h|.hpp|.cuh|.cu|.cpp files properly in our cuml C++ source base

(44 comments) (0 reactions) (1 assignee)Python (644 forks)auto 404

Build or DepCUDA / C++Tech Debtgood first issueproposal

Repository metrics

Currently, they are just all over the place! I propose the following rule-of-thumb:

If a header file contains cuda kernels and/or device methods, then it should be a .cuh.
Else, it should be a .hpp (if the current header file is already named as a .h, feel free to leave it as it is, in order to minimize the amount of ripple changes this will cause).
If a header file is used to declare our C interface, it should be a .h
If the header file includes a .cuh, then it should be a .cuh as well
If a source includes a .cuh, then it should be a .cu, else it should be a .cpp
All source files defining our C interface should be .c

This will certainly help us in reducing compilation time as well (if we end up cleaning some of the .cu files and renaming them to .cpp).

Research direction: Identify all files with extensions .h, .hpp, .cuh, .cu, .cpp in the cuml C++ source base. Rename them according to the given rules: (1) files with CUDA kernels become .cuh; (2) else .hpp (but keep .h if already); (3) C interface headers remain .h; (4) headers that include a .cuh become .cuh; (5) sources including .cuh become .cu, else .cpp; (6) C interface sources become .c. After renaming, update all #include directives throughout the codebase to match the new file names. Use Git to track changes and verify compilation with the build system.
Tech stack: ccpp
Domain: backend
Issue type: Refactor
Difficulty: 3
Estimated time: 3-5 days
Activity status: Active
Clarity: Clear
Prerequisites: C++Git
Newbie friendliness: 60