IRC channel logs

<laikq>Ahoj! Does someone know if guile has self-documenting capabilities? I've seen `(define (...) "Documentation string!" ...)` being used, but is there a way to extract the documentation string?

<surpador>laikq: you can use `,d PROC` at the repl or (procedure-documentation PROC) in code

<surpador>,d is short for ,describe. Not sure if there's other ways, others might know!

<laikq>Wonderful!

<surpador>The module (ice-9 ls) doesn't seem to be documented in the reference manual- is it documented anywhere yet besides the source? Looking at the code for the `ls` procedure, but I can't seem to figure out how to invoke it correctly. It seems like it gives a list of names defined in a given module, which seems like it would be really useful at the repl, but calling it as e.g. (ls '(ice-9 popen)) doesn't seem to work.

<Aurora_v_kosmose>ArneBab: Do you tend to use dumb-jump with geiser?

<Aurora_v_kosmose>Oh, it has a minor-mode to help with conflicts, that'd work.

<chrislck>any one knows magic to dump all available modules?

<Aurora_v_kosmose>chrislck: You'd probably have to tap into whatever whatever functions & packages guile uses to search your load path.

<Aurora_v_kosmose>Anyone knows what feature guile-fibers required that wasn't available in earlier versions?

<Aurora_v_kosmose> https://www.gnu.org/software/guile/news/gnu-guile-217-released.html Ah, non-buggy migration of coroutines between threads.

<Aurora_v_kosmose>Probably fluid-ref* too, given what it seems to do.

<surpador>chrislck: Not sure if there's an official way to do it but here's a janky way using (ice-9 ftw): https://paste.debian.net/1178674

<RhodiumToad>rlb: isn't that kind of thing one of the examples of syntax parameters?

<rlb>hah, maybe? I fixed the immediate issue, but I forgot about that. Thanks, I'll refresh.

<tohoyn>sneek: botsnack

<sneek>:)

<tohoyn>is anybody going to do something with the following bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45131

<tohoyn>just made "git pull" in guile subdirectory. the bug still exists.

<leoprikler>tohoyn: in 63:11 why is language #f?

<tohoyn>leoprikler: I don't know

<leoprikler>try inserting (peek 'compute-compiler from to optimization-level warning-level opts) in system/base/compile.scm (compute-compiler)

<leoprikler>should be line 251 in the release source, dunno if something changed since

<tohoyn>leoprikler: see https://paste.debian.net/1178731/ for the output

<leoprikler>chotto matte, network being quite slow today

<leoprikler>interesting, so tree-il is resolved to a language, but bytecode is resolved to #f

<leoprikler>for reference, what'd be the trace if you compiled scheme to bytecode in one go?

<tohoyn>leoprikler: you mean from scheme to bytecode?

<leoprikler>yep

<leoprikler>currently stuck at BOOTSTRAP GUILEC ice-9/psyntax-pp.go, so it'll take some time before I can experiment on my own

<tohoyn>here: https://paste.debian.net/1178733/

<manumanumanu>Ahoy people

<emacsen>manumanumanu, hola

<spk121>I wonder collectively how many days my computer has spent compiling psyntax-pp

IRC channel logs

2020-12-29.log