IRC channel logs

2026-01-14.log

back to list of logs

<lilyp>old: it makes sense if you think about scoping: the entire module is a scope, and definition order does not matter (IIRC)
<mov-eax>Hi, folks!
<mov-eax>How bignums are implemented in Guile?
<Arsen>seems that bignums use gmp if that's what you mean
<mov-eax>Probably I mean exactly that.
<mov-eax>So, multiplication of bignums is from gmp as well, I suppose?
<old>lilyp: the thing is that, I am doing some form canonicalization at expansion time. That is, global identifier are translated to their (@ module symbol) equivalent
<old>anyway, when I encounter a global symbol from the module where the expansion happen, I can not distinguish between that and a symbol that simply not exist
<old>So I kind of just assume that if a global symbol is present, and if it was not imported, then assume it is coming from this module
<sneek>Yey! mwette is back :D
<mwette>sneek: botsnack
<sneek>:)
<sneek>mwette: Greetings
<mwette>sneek: botsnack
<sneek>:)
<lechner>Hi, using the existing Guile module system what's a good strategy to distribute and load a module that varies across architectures but should have the same module name in each architecture, please?