IRC channel logs

<sneek>mwette: wb :)

<mwette>sneek: botsnack

<rlb>I forget how to make an object "applicable", i.e. so you can say (object ..). I think we support that?

<graywolf>rlb: I am pretty sure test-runner-xfail-count is a typo, since the description matches neither 'xfail nor common sense.

<graywolf>My expectations would be that xfail should not have effect on the exit code, since they are (in my opinion) kind of pass, since the failure was expected.

<graywolf>For "expected failures that didn't fail", there is 'xpass

<rlb>yeah, I think that's where I ended up -- thansk.

<rlb>"thanks"

<mwette>deep down in code w/ no debugger :(

<mwette>(i.e., source debugger w/ full access)

<mwette>good progress w/ print stmts

<rlb>...maybe I was just thinking of applicable structs, but I though maybe goops had something similar.

<mwette>maybe variable-transformers?

<rlb>I thought maybe there was some existing goops method you could specialize for invocation, but I may also just be remembering the workaround I implemented for lokke :)

<rlb>(There it's harder because keywords and symbols have to a act as functions too.

<rlb>)

<rlb>And we definitely can't do that.

<rlb>(directly)

<sneek>Welcome back mwette!!

<chrislck>sneek: botsnack

<sneek>:)

<chrislck>^_^

<mwette>:)

<sneek>Welcome back chrislck!!

<mwette>sneek: botsnack

<sneek>:)

<rlb>Haha - I was confused by string->bytevector crashing on conversion of greek "mu" to latin-1 and about to ask for help, but after a while I figured out I had µ and not μ (sure that's not confusing at all).

<rlb>(I had micro, when I thought I had lower case mu, and the former doesn't do latin-1.)

<rlb>Finally noticed via char->integer...

<rlb> https://en.wikipedia.org/wiki/Mu_(letter)#Unicode

<rlb>I should probably see about an example without (or with less common) homoglyphs...

<rlb>Sorry, I meant the reverse, micro is in latin-1, lower case mu isn't.

<ajr>hey everyone, quick question about stack traces in guile scheme - https://pastebin.com/z9m0ewXg

<sneek>Welcome back ajr, you have 1 message!

<sneek>ajr, notmaximed says: ^ https://logs.guix.gnu.org/guix/2021-11-28.log#230623

<ajr>this is just sample code, maybe it's not a problem in practice?

<mwette>ajr: What's the question?

<mwette>you can try adding `--debug' to guile: #!/bin/sh\nexec guile --debug $0

<mwette>that might give more, but not sure what ur after

<ajr>(b) and (a) are not included in the stack trace (i think due to tail call elimination). "--debug" doesn't seem to affect it.

<ajr>curious if there's a way to have those preserved for debugging.

<mwette>If the code is in a .scm file you can try to compile w/o optimization : `guild compile -O0 file.scm; guile --debug file.scm'

IRC channel logs

2025-12-07.log