KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
EGL: extensions-compactness of implementation
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The safety environment requires from implementation to be compact in several forms: to be relatively simple, to have simple management of resources, to offer simple API, to occupy relatively little memory and execute fast and to be guaranteed to be free of any runtime issues which could compromise safety requirements. Adding new extensions to a standard could make this implementational compactness hard to maintain.
For reference, general issue "EGL: extensions" is defined as issue #40.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading this issue alongside the referenced general issue #40, since no file, test, or entry point is named. Determine what concrete guideline change is needed to address implementation compactness when extensions are added; done requires an agreed, documented outcome rather than only a general concern.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100