KhronosGroup / KhronosGroup/OpenCL-Docs
Unified API Spec: Consider a Removed State
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
During review of the initial draft of a unified API specification there was a question [1] about have a removed by state. OpenCL has not been explicit about removing things previously, though pragmatically I expect some aspects will not be present in any modern implementation.
This ticket is to first gather together a plausible list of "removed" features (i.e. features that were deprecated and are no longer present in modern implementations), and second to propose a way of representing this in the specification.
[1] https://github.com/KhronosGroup/OpenCL-Docs/pull/78#discussion_r334985389
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 with the initial draft of the unified API specification and the discussion in pull request 78 linked from this issue. Compile a plausible list of deprecated features absent from modern implementations, then document a proposed way to represent a removed state; done means both the list and representation proposal are recorded for review.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100