IRC channel logs

2022-07-11.log

back to list of logs

***X-Scale` is now known as X-Scale
***X-Scale` is now known as X-Scale
<lloda>nested defines are easier to manipulate than let. You can move stuff in and out of a scope by simple c&p
<lloda>i've been using them a lot recently
<lloda>it's very handy when you're trying stuff and you aren't sure yet where things should go
<amirouche>indeed
<amirouche>it also useful to group stuff together, something that is done with OOP classes very often e.g. private methods, when a procedure is used only inside another procedure, it leads to extra cognitive load to define it at a top-level, or worse in a helper.scm library, instead, when a procedure is useful only inside another procedure, just nest it!
<civodul>because i'm a nice person, i haven't remove 2.0 support in GnuTLS
<civodul>but now i find myself writing things like SCM_TYP16 (port)
<civodul>and i can feel how bright the present is
<civodul>comrades, i submitted changes to GnuTLS that should allow us to get rid of the port wrapper in the 'tls-wrap' procedure in (web client):
<civodul>1. https://gitlab.com/gnutls/gnutls/-/merge_requests/1609
<civodul>2. https://gitlab.com/gnutls/gnutls/-/merge_requests/1610
<civodul>in particular, that should let us use session record ports in a non-blocking context with Fibers (though i haven't tested that yet)
<civodul>feedback welcome!
<drakonis> https://dustycloud.org/blog/guile-steel-proposal/ this is a nice post.
<dsmith-work>Morning Greetings, Guilers
<dsmith-work>I so read that as "Guy Steele"
<sneek>wb tohoyn!!
***Guest927 is now known as chrislck
<chrislck>nested defines are also better for lambdas... having numerous (let ((proc1 (lambda (arg) ...)) (proc2 (lambda (args) ...))) is tedious
<unmatched-paren>chrislck: yeah. i don't really understand why (let (((func param1 param2) ...)) ...) isn't allowed
<daviid>chrislck: those are equally bad, imo, in terms of programming style, they are 'the same thing' ... i'll answer earlir comments later, i just wanted to quickly make this point ... happy hacking all, bbl
<gabber>xiews: WDYM? i can see relevant bingings with ,b within the module, but the output ("#<variable 7f29657b3f40 value: #<procedure foo-func-name ()>>") lacks information on /where/ this variable was bound/imported from
<dsmith-work>And even closer to "Guy L. Steele"
<dsmith-work>Intentional?
<drakonis>dsmith-work: yes
<drakonis>read the post
<dsmith-work>Doh! I *did* read it. But must have missed or forgotten that part!
<dsmith-work>The other day I was walking around looking for my rain jacket, and it was on my arm...
<dsmith-work>This does *not* bode well..
<drakonis>old age plagues you?
<drakonis>or worse, various brain issues?
<dsmith-work>Getting up there. 62