Inconsistency on Vulkan Format enum

[gdkchan]

Summary of feature

Currently there's a small inconsistency on the Format enum names. The snorm formats have the N capitalized, so they are SNorm, while the unorm ones aren't.

Example:

B8G8R8A8Unorm
B8G8R8A8SNorm

I propose changing them to:

B8G8R8A8Unorm
B8G8R8A8Snorm

So basically, changing SNorm to Snorm.
For consistency. I hope it's not too late to do this kind of breaking change on the library.

[Perksey]

This depends on how they're defined upstream. We're fine with upstream-induced breaking changes such as these, but if how we're parsing it is consistent with upstream then it'd be much harder to justify such a break.

Will investigate and get back to you.

[Perksey]

Ok so it looks like we actually special-case SNorm here. @HurricanKai do you think it's worth a break in 2.x? Also, should we discuss with the working group as this will affect OpenGL too?

[HurricanKai]

Can't we just add the Snorm in 2.next and mark the SNorm as obsolete (and hide it from intellisense?), then remove the SNorm in 2.(next + 2-5)?

[Perksey]

That would be a very involved change, the current BuildTools pipeline doesn't really suit token overloading like that.

[HurricanKai]

Don't you think for this case we can just make that change manually? Otherwise I'd be unhappy to break, since SNorm/Unorm are basically everywhere in Vulkan code.

[Perksey]

We can just save this for 3.0, adding a lot of code just for this issue into BuildTools doesn't seem worth it.