pub const FRAGMENTS: &[(&str, &str)];Expand description
The shared fragments, as (marker, file). A shader carrying a marker has the named file’s text spliced in at that point.
Three of them come in pairs, because a shader’s resource bindings sit between the halves: MAIN_TYPES / PROBE_TYPES / RT_TYPES declare the records a binding names, and MAIN_SHADING / PROBE_COMMON / RT_TRACE the code that reads the bound resources.
PARTICLE_TYPES is the one shared by two halves of a system rather than of a shader: the simulation kernel writes the pool the render pair reads.
The order is load-bearing where one fragment carries another’s marker: the splice runs the table once, so a nested marker is only replaced if its own row comes later.