Published 1.5.1 broke public API about rspirv

[antiagainst]

That comment was made quite some time ago when we saw the first breakage. Things do change and I'm certainly not trying to hold back improvements. :) We had similar discussions in another thread later (see here) where I suggested to retire the spirv_headers create and use the spirv crate instead to have a clean slate for using semver. This might be the time to really push towards that.

[Jasper-Bekkers]

@antiagainst Agreed, filed #197 for further discussion around how to proceed :-)

[Jasper-Bekkers]

spirv_headers don't follow semantic versioning so breakage like this is sort-of unavoidable without some changes to the policy of this project :-(

We've run into this before with #117

[Jasper-Bekkers]

For reference - required_capabilities and required_extensions got moved into Operand instead because there can be multiple capabilties or extensions required.

[kvark]

Wait, #117 was actually fixed, and sanity was restored. Are you saying that the current breakage is intended?

[Jasper-Bekkers]

In #117 a workaround got introduced to not break semver, however in this case I'm not sure we can (see previous comment).

[Jasper-Bekkers]

It's specifically this comment that explains why we're in this spot though I'm not a big fan (for obvious reasons).

[ErichDonGubler]

Given that #197 is closed now, does that this mean issue is resolved?