-
Niklas Haas authored
For shaders which require access to "configured" objects, this tracks the object's lifetime and allows the shader to re-use the same configured object across frames, with the caller being responsible for cleanup. Not entirely sure if I want to just chuck everything in there or do subtyping via void *priv, but I think for now the chuck-everything approach is fine.
04bc66cb