KhronosGroup / KhronosGroup/OpenCL-CLHPP
Revisit how we handle deprecated functions
Open
- Dominant language
- C++
- Stars
- 425
- Forks
- 133
- Avg merge
- 3h 30m
- Merged PRs (30d)
- 1
Description
Do we really need the bindings to be declared as "deprecated" when the underlying CL function already is?
See discussion on https://github.com/KhronosGroup/OpenCL-CLHPP/pull/129
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the discussion in pull request 129 and locate how the C++ bindings declare deprecated functions relative to the underlying OpenCL C functions. Determine the desired deprecation policy and identify the affected binding declarations; done means the policy is agreed and the declarations consistently reflect it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100