Khronos asking for feedback on removing BEGIN_RANGE / END_RANGE / RANGE_SIZE tokens from headers

Shortly after 2020-04-24, we will be removing the automatically generated VK_BEGIN_RANGE, VKEND_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 this issue, but we strongly suggest any external projects using these tokens immediately migrate away from them.

If you absolutely require these tokens in your headers for some reason, your best option going forward will be to generate your own headers using a process TBD as we get closer to 2020-04-24 (probably by providing a means to restore the old behavior of the scripts which generate these tokens).