Javelin requirements about rspirv

[antiagainst]

I think as discussed previously, most of the tasks here are depending on a good structured representation and general infrastructure for analysis/transforrmation passes, execpt for 1), which right now we have a working solution. The existing parser and data representation was designed to provide good error handling (w.r.t. which word is problematic, etc.) but it completely ignores debug information (OpLine, OpNoLine, etc.) and that's something should be fixed to provide even better error reporting experience. However, I think this is something we can defer until we get the structured representation and general pass infrastructure ready and have at least one example working e2e.

[Jasper-Bekkers]

@kvark @antiagainst now that this development has moved to naga, can we close this?

[antiagainst]

Nice! Thanks for writing this down, @kvark! It is much clear this way for everyone to understand the use cases we are driving for. We can use this as a master issue for other tasks and we might want to use GitHub Projects to organize certain tasks.