Pierre Krieger
Pierre Krieger
Hmm you have a different approach than what I was thinking of. In my mind, the `module` member of `ShaderEntryPoint` would become a `Cow`, so that the `ShaderEntryPointLoad` trait can...
Note that any change you make to `vulkano-shaders` will likely heavily conflict with some changes I'm going to make in the `incoming` branch. Please tell me if you start anything...
> Can the current implementation lead to invalid API usage? No. [The code](https://github.com/vulkano-rs/vulkano/blob/06a0b3715ff235ce78c4f50e580134467be44ef0/vulkano/src/command_buffer/auto.rs#L1073-L1091) only uploads the ranges corresponding to the ranges of the pipeline layout, and the pipeline layout itself...
> Correct? Yes. Also note that vulkano-shaders will generate a struct a compile-time that you can use.
That's unfortunately not implemented yet, because it's not trivial.
My latest contribution is from April 2015. I don't think I can be considered a maintainer.
This is probably https://github.com/tomaka/winit/issues/79 Also you should try running valgrind on a non-Rust OpenGL application to make sure they are not a problem in the OpenGL driver instead.
You should definitely be able to share the same image between descriptor sets and framebuffers (as long as you don't use them simultaneously). Theoretically vulkano allows that, but in practice...
Latest commit depends on https://github.com/vulkano-rs/vulkano/pull/787 to build.
@alteous Sure.