IRC channel logs

2021-06-22.log

back to list of logs

***terpri is now known as robin
***sneek_ is now known as sneek
<rlb>wingo: bisect points to 0cc799185576712d69f11fc794454f2f5447bef7 as the commit where that #nil macro issue appeared.
<wingo>interesting
<wingo>rlb: to my mind, all of the null? calls in psyntax.scm:2880-3019 (the pattern matcher used by syntax-case) should instead be eq-null?, defined as (define (eq-null? x) (eq? x '())
<wingo>#nil should probably never match () from the POV of syntax-case
<wingo>dunno, i guess i can see the argument for building scheme expressions from elisp, but really i think it's not too much to ask to use the "right" EOL in that case, dunno
<wingo>if we wanted to relax that stance, we could use eq-null? only when dispatching on patterns, but null? on incoming syntax
<taylan>wingo: rlb: I seem to have missed part of the conversation here so dunno if these came up:
<taylan> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48315
<taylan> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48425
<taylan> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48318
<taylan>wingo: also, I sent quite a few patches to the bug tracker a couple weeks ago, hope they don't get forgotten :)
*taylan gtg
<rlb>wingo: hmm, I'll need to understand what you've said more carefully later, but here's where I was using that check: https://git.sr.ht/~rlb/lokke/tree/main/item/mod/lokke/base/util.scm#L61 which is used in methods like this: https://git.sr.ht/~rlb/lokke/tree/main/item/mod/lokke/base/collection.scm#L712
<dsmith-work>Tuesday Greetings, Guilers
<thmprover>Random question: what's the convention for guile docstrings? I couldn't find it in the reference manual...
***RhodiumToad_ is now known as AndrewG
***AndrewG is now known as RhodiumToad_
***roptat is now known as roptat_
***roptat_ is now known as tyreunom_
***tyreunom_ is now known as tyreunom
***tyreunom is now known as roptat
<leoprikler>thmprover: You can choose between Emacs-style "Frob VAR." and texinfo-style "Frob @var{var}."
<leoprikler>both are accepted and which you prefer somewhat depends on your tooling
<tohoyn>sneek: botsnack
<sneek>:)
<thmprover>leoprikler: for texinfo-style, can I use *any* texinfo commands? Or is it a restricted subset of texinfo? Specifically, is there a way to encode math?
<leoprikler>Again depends on your tooling, but AFAIK the texinfo module from Guile should not interfere with your math code
<leoprikler>Try object-stexi-documentation to get a closer feel
<thmprover>Awesome, thanks!
<mwette>thmprover: github.com/mwette/guile-contrib/scheme-texidoc.el is (non-robust) minor mode that will take comments in texi format preceeding a function and turn them into a doc string pasted as the first expression in a function body
<mwette>look at the bottom of this file: https://git.savannah.nongnu.org/cgit/nyacc.git/tree/module/nyacc/parse.scm
<thmprover>mwette: interesting, thanks!