IRC channel logs
2025-01-24.log
back to list of logs
<sneek>I've been faithfully serving for 5 days <sneek>This system has been up 5 days, 11 hours, 32 minutes <cow_2001>rlb: i did not implement it, so i would have to reimplement it in goop, which is good - i would have to read the goop documentation. thank you! <cow_2001>are there any good reasons NOT implementing it in goop and extend it using some other means? <rlb>cow_2001: Ahh, I suppose that's the reference implementation. And I'm not sure. Aside from whether or not guile wants those functions to be extensible, I don't know how goops interacts with compiler optimizations right now, as compared to what I imagine is likely a big "switch statement" in the srfi code. I also hadn't noticed it has a registration function, so consider my comments not entirely well informed... <carloratm>I got my hands on a used copy of The Little Schemer. Do you believe I could use that as an introduction to guile? <ray1729>carloratm: it's a fun read and helps understand scheme, but it's not a practical introduction. <vbramselaar>specificly I want to calculate the length of the args at compile time as you can see in the output at the bottom <vbramselaar>any feedback for this? I had a pretty hard time to figure this out in syntax-rules. <vbramselaar>btw I know that "average" does not need to be a macro but just for exercise. <vbramselaar>is that the way to go if you only want to use syntax-rules? <mwette>I think the key w/ syntax-rules is you want the compiler to pre-compute the count via optmization. <vbramselaar>mwette: so it recusively creates syntax for the count? interesting, makes me think of c++ template recursion to simulate a loop. <mwette>You can check. The repl has some tools to explore: ,expand (ave 1 2 x 4 5) and ,optimize (ave 1 2 x 4 5)