Is it ok for Vulkano-shaders to depend on Vulkano?

[Rua]

@AustinJ235 @Eliah-Lakhin I would like to start moving some of the code in Vulkano-shaders to the main Vulkano crate, so that it can be used both by runtime-loaded shaders and shaders compiled with Vulkano-shaders. But to avoid duplication, Vulkano-shaders would need to be able to import some of these items from the main crate. It currently lists Vulkan only as a dev-dependency, but I would like to upgrade this to a full dependency. This would mean that Vulkano-shaders can't be used without Vulkano anymore, but I think that's ok because it outputs Vulkano-specific code anyway and wouldn't be particularly useful without it.

[Eliah-Lakhin]

@Rua I think that's fine. But can you please outline what particular changes are you going to do? The thing is I'm currently working on some Vulkano-shaders improvements too.

[Rua]

• Implementing Make shader data generation available at runtime #1558
• See if I can generate some of the types such as Instruction automatically from the SPIR-V grammar JSON file.
• Build up a bit of information at parse time, such as the location of each ID, and a list of any annotations (names, decorations) it has. Also making a list of sections in the module, as described in "2.4. Logical Layout of a Module" in the SPIR-V spec. This is mainly so that later searches don't have to iterate through all the instructions each time, but can find what they need more quickly.

There is no hurry though, I haven't done any work yet so I'll wait for you to finish.

[Eliah-Lakhin]

@Rua ok, sounds good. Just to let you know that I'm currently working on extension of vulkano-shaders to compile several sources at once producing independent generated layout per each source, but keeping all their structs in a single shareable generated ty mod. This feature should resolve a long-standing problem of type-safe interoperability between generated shaders. I probably will finish this work today and provide a PR.