Remove advanced notice of header change
The BEGIN_RANGE, END_RANGE, RANGE_SIZE enums have now been removed from the headers, per https://github.com/KhronosGroup/Vulkan-Docs/issues/1230, so remove the "Advance Notice" from the README.
This commit is contained in:
parent
0c5351f5e9
commit
9250d5ae8f
14
README.md
14
README.md
@ -2,20 +2,6 @@
|
|||||||
|
|
||||||
Vulkan header files and API registry
|
Vulkan header files and API registry
|
||||||
|
|
||||||
## Advance Notice of Pending Header Change (posted 2020-04-06)
|
|
||||||
|
|
||||||
Shortly after 2020-04-24, we will be removing the automatically generated
|
|
||||||
`VK_*_BEGIN_RANGE`, `VK_*_END_RANGE`, and `VK_*_RANGE_SIZE` tokens
|
|
||||||
from the Vulkan headers.
|
|
||||||
These tokens are currently defined for some enumerated types, but are
|
|
||||||
explicitly not part of the Vulkan API.
|
|
||||||
They existed only to support some Vulkan implementation internals, which no
|
|
||||||
longer require them.
|
|
||||||
We will be accepting comments on this topic in
|
|
||||||
https://github.com/KhronosGroup/Vulkan-Docs/issues/1230, but we strongly
|
|
||||||
suggest any external projects using these tokens immediately migrate away
|
|
||||||
from them.
|
|
||||||
|
|
||||||
## Repository Content
|
## Repository Content
|
||||||
|
|
||||||
The contents of this repository are largely obtained from other repositories and are
|
The contents of this repository are largely obtained from other repositories and are
|
||||||
|
Loading…
x
Reference in New Issue
Block a user