shader-slang
[Tutorial] Write tutorial pages for compilation API
We need tutorial pages for people who want to learn about the compilation API. The tutorial should also reflect some of high level principles of Slang language design that Tess presented at a recent brown-bag.
Specifically we need to fill in the TODO sections in a commit.
There are multiple "TODO" lines in the commit. This issue is for the following sections:
@csyonghe Is there any particular quality you're looking for in the tutorial? https://shader-slang.com/slang/user-guide/compiling.html#using-the-compilation-api nearly reads like a tutorial already and as I'm writing my content, I'm finding it hard to distinguish it from the user-guide.
I was thinking that it should be focused on getting one short example working, step-by-step, explaining the parts, as opposed to trying to explain everything you can do.
Does it need to be of a sufficient complexity to require linking, specialization, preprocessor macros, or should it be as small as possible?
WIP https://github.com/cheneym2/shader-slang.github.io/blob/cheneym2/compile_tutorial/docs/compilation-api.md
Please create a PR for this so we can put in review comments.
This document should aim to be as comprehensive as possible.
Given that the goal is to be comprehensive rather than an introduction, it definitely needs work.
Trying to add directions for specialization, but in writing a very simple app to compile, it fails.
Filed https://github.com/shader-slang/slang/issues/5653