let it leave me like a long breath

as far as i could tell, uniforms don't work in lambdacube. i was never able to get any uniform aside from a single float (no vectors or anything else, and not even two distinct float uniforms) working. there was only minimal documentation as to what the correct format to specify uniforms was, and apparently at some point the lambdacube devs rewrote all their demo applications to only use a single float uniform, so i couldn't reference off of those either. other, older demos used an entirely different way of specifying uniforms, which i also tried since the code to do that was still in the library, also to no effect. i'm still not sure if the problem was "the library broke its uniform support" or "i'm doing something wrong when i specify uniforms".

also, when these errors happened, the actual thing that happened was that the program crashed with weird debug messages talking about the raw parse state of the lambdacube pseudo-haskell shader language, in terms that none of its documentation ever mentioned. there was very little documentation of what the syntax of its shader language even was, and i had more than a few problems that were caused by weird type inference in the shader that seemed to magically appear and disappear when i made changes that didn't seem like they should have changed the inferred type, and there were a few notes about how lambdacube didn't actually do any typechecking for its uniforms at all, which meant that you could declare uniforms as anything and it would happily typecheck, which also made figuring out if i was doing anything wrong much harder, so attempting to debug anything was very confusing and weird.

anyway eventually i gave up and started using gpipe and that's gone a lot more smoothly.