Awkward generated name in PhysicalDeviceLimits::max_image_dimension1_d

[Rua]

I'm assuming that this is a mishap with some kind of auto-generating script, and that it should really be max_image_dimension_1d or max_image_dimension_1D. The same happens with 2_d and 3_d, and probably other occurrences of this elsewhere. It would be easy to fix with a PR, but I want to report it in case the thing that produced these names needs fixing.

[MaikKlein]

Thanks, I wasn't aware of this. Seems like we generated max_image_dimension1d in the past, but it should be max_image_dimension_1d.

[MarijnS95]

That looks to be intended by snek, inserting an _ between a number followed by an uppercase letter. Responsible bit is here if you want to patch it:

https://github.com/MaikKlein/ash/blob/b3a010a3154d0cd9d4943e794a0e90916da93936/generator/src/lib.rs#L725-L732

[aloucks]

At one point I was building a generator and had some functions for name conversion that handled a bunch of weird edge cases in vulkan names. It's posted in this gist if you're interested.