Search
Sunday, 23rd of January 2022, 14:30:15 UTC
15:27:09
lisp123
pjb: Do you remember what your lambda list parser was called? Trying to find it now as its v. useful for macro writing
15:28:15
phoe
lisp123: for what kind of lambda lists?
15:28:30
phoe
alexandria:parse-ordinary-lambda-list is for ordinary ones, can't say anything about others though
15:28:56
lisp123
phoe: Just being able to split (required &optional &rest etc.)
15:29:03
lisp123
Oh thanks, I'll check that out too
16:00:50
jmercouris
lisp123: I think it is cesareum or something
16:01:02
jmercouris
The string isn’t coming to mind exactly
16:01:19
lisp123
jmercouris: Thanks! Yeah that must be it
16:01:37
jmercouris
lisp123: if you want an example, we use Alexandria in the Nyxt codebase to split lambda lists
16:01:58
lisp123
jmercouris: Nice one, I will check it out
16:02:58
jmercouris
https://github.com/atlas-engineer/nyxt/blob/master/source/command-commands.lisp
16:31:18
pjb
lisp123w: com.informatimago.common-lisp.lisp-sexp.source-form:parse-lambda-list
16:31:36
pjb
it's easy: just load com.informatimago in your rc file, and then you can (apropos "whatever").
20:21:37
attila_lendvai_
** NICK attila_lendvai
20:29:13
huckleberry
I've been using closures as pseudo-streams (basically generators) in a lot of projects instead of separate state objects. I haven't really noticed an issue with speed but should I be doing that or should I be using separate state objects i.e. gray streams?
20:30:15
mfiano
Gray streams/generic functions allow for flexibility and extensibility.
20:30:40
mfiano
I would much prefer them over a closure that is hard to debug/poke at from the outside
23:00:13
EdLangley[m]
(eval (capi:prompt-for-form "CL-USER>"))
23:20:38
bollu
Oh neat, "Gray" is after the person who invented the CLOS spec for how streams "should" be?
23:38:02
moon-child
I thought it was 'gray' as in 'gray water'
23:54:12
dbotton
Xach when is the next quicklisp release coming up?
Monday, 24th of January 2022, 2:30:15 UTC