Update Vulkan-Headers to 1.3.206

[MarijnS95]

Vulkan 1.3 is out, with many extensions stabilized. This'll have to remain draft until the next spec version (hopefully next week) where (again, hopefully) KhronosGroup/Vulkan-Docs#1746 is incorporated - otherwise we'll have to work around in our generator :(

[MarijnS95]

Can't update to 1.3.205 either, vk.xml got broken there as well: KhronosGroup/Vulkan-Headers#258 (comment)

[Rua]

Seems to have been fixed in KhronosGroup/Vulkan-Docs#1764.

[Ralith]

If it wasn't clear, I think this is a breaking change, because e.g. Extends* for structs that were made core have been renamed.

[MarijnS95]

@Ralith Do we think that's a problem, or an unsafe implementation detail? After all, callers are not supposed to implement these on their own. However, crates may also decide to use these trait bounds for their own purposes (perhaps something that "wraps around" push_next).

I'm thinking about getting a patch release out now then, and release a breaking release with Vulkan 1.3 and the rest shortly after. It's a large update that "deserves some attention" anyway.

[Ralith]

It's definitely a technical semver break, since it is legal (regardless of unsafe) for downstream code to reference the changed identifiers. I think the real-world impact is probably low, but I also don't see a need to play fast and loose with semver.

[MarijnS95]

Should have probably not mentioned unsafe implementing the traits by clients at all (which I can't see any valid reason for), since being able to use this trait bound in a safe wrapper is already well enough of a possibility to risk an API break.

I don't want to go figure out how to add a bunch of type aliases for these either, at least :)

[Ralith]

Yeah, I don't think that's worth the trouble; this only comes up on Vulkan minor version bumps anyway.