Dimitri Sabadie
Dimitri Sabadie
#96 is going to bring those to the next release. :)
Nah leave it open, we’ll close it whenever we have more test data and usage. You’re very welcome.
Feel free to tell me whenever you have time if your issue is fixed with `glsl-3.0`. :slightly_smiling_face:
Yes, unfortunately, those are currently only supported at the top-level of your shader.
Hm, I need to have more information / find more material about that symbole table they’re using. Do you have any link?
@jrmuizel great! I haven’t had enough spare time lately to look into that, but feel free to go for it! I’ll have a look at the code you wrote, I’m...
It’s not an alias anymore, but type safety is not enforced. We have to take care of that.
The branch `spir-v` contains an untested initial implementation against [shaderc](https://crates.io/crates/shaderc). The idea is to first test with that backend. We will write the semantics analysis later as it will depend...
Hm, yeah, I would also like to have that too, but I still don’t quite know how to, since it would be possible to interleave the AST with it.
Having the start and end positions in the input slice would definitely help, that’s for sure.