Baggers

SDL2 is going to dictate the implementation as it only shares with a 'current' context. Most apis can take the context as an argument so who knows why they chose...

Better error message for invalid :attachment-for-size in with-fbo-bound

2

- create an fbo with only a depth attachment - use it in with-fbo-bound - Note the poor error message. What is happening is that it is trying to set...

:unsigned-int-24-8 is the blighter

Simple mistake, I'm using the slot names as var names in a struct and this causes issue when t is used. gensym that shiz ``` (defstruct-g (erosion-uvs :accesors nil) (l...

use print-unreadable-object

1

I didnt know about this, looks useful. I can use it in all print-object definitions. also read https://github.com/scymtym/utilities.print-items and see if it would be useful too.

Look into this macOS resolution bullshit

1

https://github.com/glfw/glfw/issues/422

Go reading about downsides for this, it feels like a good default

Don't print gpu-func compile messages to *standard-out*, use something quieter

2

I'm not sure what the correct approach is for this. I'll ask on IRC later