KhronosGroup / KhronosGroup/OpenCL-Docs
Should error code enums be reserved in blocks of 1, 10, or 16.
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
Currently error codes are reserved as they come (i.e. generally a block of 1). If we keep doing that then this issue can close with no action.
If we want to reserve them in blocks of 10 or 16 then that reservation should be made, and currently either is numerically possible.
See discussion on a PR for merits of either approach: https://github.com/KhronosGroup/OpenCL-Docs/pull/244#discussion_r396605609
Contributor guide
Research direction
Start with the discussion linked from PR 244, especially the referenced review thread, to understand the merits of reserving error codes in blocks of 1, 10, or 16. The issue is done only when one policy is decided and the relevant error-code reservation sources are updated, or the issue is closed with no change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100