Baggers

Use varjo type objects everywhere we can in CEPL rather than type-names

2

This mainly applies to pipelines & stages spec objects. It's a bummer to have to fart around with these in their base form.

https://mesamatrix.net/ llvmpipe is the one we want See https://github.com/fusetools/fuselibs-public/blob/master/appveyor.yml for usage We don't do enough testing on windows so this could be a really sweet little setup

print in shaders :)

2

This is madness but could work. draw twice, once normally and once for debug. we use varjo to strip down the shader so it removes all parts of the shader...

`*compile-file-pathname*` & `*compile-file-truename*` can both be captured at first compile time and then we can shadow these in the recompile to see what the effect is

For blending-params copy a bunch of the stuff from the struct definition. It just helps to have it in the func too. For clear, explain that the W component is...

This is what i'd expect but not what happens

`(cepl.fbos::%make-default-framebuffer dimensions t t))` This is crap though, the dimensions of the default fbo in this case is `window-dimensions` May need some special casing, get on that.

This means we can add defines & bootstrapping code in the inline string and pull the rest from the file. We should also generate a recompile function so that users...

very unforgiving lack of type error on make-c-array

1

very unforgiving lack of type error on make-c-array ``` ARRPG> #((1 2) (3 4)) #((1 2) (3 4)) ARRPG> (make-c-array * :element-type :vec2) # ARRPG> (aref-c * 0) #(1.6630957e-34 2.2420775e-44)...

Add more pixel-format <-> image-format mappings

1

We should be more thorough, there are plenty we could handle. We should make some cepl structs for the packed versions. Then we can set this as the type (which...