20:30:58didiIndeed. I learned *print-length* recently. Very nice feature.
20:31:11phoe_if you're worried about it, you can defstruct and still get good performance, and then define a print-object method on it that does not print everything like crazy.
20:31:25phoe_and if you want to use full CLOS trickery, go with defclass.
20:33:35phoe_Go with defclass, and if you feel that your performance suffers way too much AND that you are not using too much CLOS magic, then go for defstruct instead.
20:37:55phoe_XachX: actually, now that I think of it.
20:38:11phoe_I could use VECTO, if there was a way to get the in-memory vector of data *before* it's saved into a PNG.
20:38:25phoe_There's no exported function for that though, for getting the raw array of ARGB.
20:43:48phoe_It seems that I can use an unexported IMAGE accessor, https://github.com/xach/vecto/blob/8659770bfdc460a1c6b07271a188ec6c19aad3ea/user-drawing.lisp#L332
20:47:32phoe_there, https://github.com/xach/vecto/pull/7 <- catch a PR from me.
20:58:20phoe_XachX: If I understand VECTO correctly, I can call SET-GRADIENT-FILL to describe what kind of gradient I want, and then call RECTANGLE to bound that gradient to a particular space on the canvas, so it doesn't draw the gradient all over the previous gradients I have created on that canvas. Is this correct?
0:03:13sebbohhm, didn't work for some reason. The UI prompted me to confirm the name of the thing I wanted to fmakunbound, but it still has a value... Oh well, it's quittin' time. :)
5:32:22beachminion: Please tell iqubic about Cleavir.
5:32:22minioniqubic: Cleavir: A project to create an implementation-independent compilation framework for Common Lisp. Currently Cleavir is part of SICL, but that might change in the future
5:32:28beachminion: Please tell iqubic about SICL.
5:32:28minioniqubic: SICL: SICL is a (perhaps futile) attempt to re-implement Common Lisp from scratch, hopefully using improved programming and bootstrapping techniques. See https://github.com/robert-strandh/SICL
6:18:39beachIn fact, that inlining technique creates functions with multiple entry points. Such functions can not be expressed as Common Lisp source code, but there have been languages that allow such functions of course.
6:21:58lokebeach: Which languages are those? (except Assembler)