Establish a coherent user-facing C++ API for cuML with explicit validation, documentation, and stability guarantees.
The current C++ interfaces have different levels of maturity and are primarily intended to support cuML's Python implementation. Carve out a clearly identified user-facing API and gradually migrate suitable interfaces into it. Existing interfaces remain internal unless they explicitly graduate.
This effort should:
- Define the namespace and organization of the user-facing API.
- Establish validation, error-handling, stability, and deprecation requirements.
- Define the criteria for graduating an interface.
- Identify migration candidates and track them in scoped follow-up issues.
- Separate user-facing API documentation from the internal API reference.
Related developer-documentation work: #8590
Establish a coherent user-facing C++ API for cuML with explicit validation, documentation, and stability guarantees.
The current C++ interfaces have different levels of maturity and are primarily intended to support cuML's Python implementation. Carve out a clearly identified user-facing API and gradually migrate suitable interfaces into it. Existing interfaces remain internal unless they explicitly graduate.
This effort should:
Related developer-documentation work: #8590