i havent used declare before and relied only on using def and hoping for the best, so far. i am working on a wgpu binding written with cjanet right now, managed to init, terminate and create a window using glfw3 in my free time, at work i used cjanet to implement the first couple functions for a hdf5 binding and already i am thinking about that json file describing the raylib api...

that would be just for fun though...blasting through a json dict and generating code to look through.... i would be done with wjpu before i started that... right?

just now i spotted an error in some handwritten sourcefile in which i had started work on wjpu (my wgpu binding for janet): I had written the destroyWindow binding with an arity of 0, such a silly mistake couldnt really happen over in cjanet land... surely, i copied the fixarity line from somewhere else in my code and hoped to adjust it each time correctly after pasting... over in cjanet land, i can just almost write c-code, but in a janet-y way. once i run it, the generated c code for the bindings is written into a file compiled and i also check each newly written function and adjust the cjanet script until im happy with the results.. the best thing is, it handles the arity shebang and wraping and whatnot for me, of course once i have to handle datastructures it might get hairy, but even there it seems to be pretty straight forward.

in a way, it feels like you can do more while potentialy breaking less.

i need to get this into some kinda usable condition, with a demo and or examble etc pp. before i post something on some source controll thing. though i do have it in my monorepo