Which operations will make use of the sessionDesc.fileSystem object?

[mbechard]

Hey,
My application is a GUI tool for users to create real-time visuals. The end-users edit shaders in the GUI, and compilation automatically occurs as soon as they click-off the editor window.
#include and import statements can reference other blocks of code that defined in their project, not sitting on the OSs filesystem.
To enable includes with this workflow, I make a custom fileSystem implementation that resolves the include paths to other text blocks in the project.

This resolution needs to occur in the main thread, since I want the shader to be resolved in the state the code was when they stopped editing, not a little later which may incorporate changes to the included files that happened afterwards. I want to do as much work involved with the shader compilation in another thread though, in particular the SPIR-V optimization passes.
My workflow involves:
For each shader stage:
loadModuleFromSourceString(), findEntryPointByName()
Followed by single calls to
createCompositeComponentType(), composite->link()

Is it safe to assume the fileSystem object is only used in the first set of operations, and isn't used anymore for the composite/linking? The goal would be to move the linking to another thread.

Thanks

[csyonghe]

IIRC the file system object will no longer be used after calling loadModule, and you should be able to assume no more file IOs after the last call to loadModule* functions.