Conversation

Notices

1. Embed this notice
   mousebot (mousebot@todon.nl)'s status on Friday, 08-May-2026 01:18:41 JST mousebot

   man, #guile #scheme is v cool, v v good.

   (but also, i really really struggle with the absensce of nil punning. instead of nil everywhere have '(), \#f, and the dreaded \#<unspecified>. why on earth would i want my when clause to return the latter when it could just return nil? i can't fathom it.)

   but guile v cool, v v good.

   (now i'm gonna turn into one of those folks dreaming about guile emacs, coz it if worked out you'd imaging writing all your extensions and packages and hacks in this elegant motherfucker of a lisp...)

   • Embed this notice
     Janneke (janneke@todon.nl)'s status on Friday, 08-May-2026 01:18:39 JST Janneke

     in reply to

     @mousebot
     Less "happy" accidents? Stricter typing is mostly better?

   • Embed this notice
     mousebot (mousebot@todon.nl)'s status on Friday, 08-May-2026 01:29:40 JST mousebot

     in reply to

     • Janneke

     @janneke given how carefully it is made, i have to assume the guile makers know what they are doing (and i know them and know that they do), and don't doubt that there are good reasons. but i'm very used to nil punning like the blazes, i find it elegant. without it, when/unless become unusable to me.

     i also don't see why we need three nonentities. can't your queries be satisfied with 2? calling (unspecified?) on something is a monstrosity.... why not return false for a failed when?

     but anyway, guile v v good :), maybe one day i will see the light re holy prohibition on nil punning!