IRC channel logs
2016-09-04.log
back to list of logs
<paroneayea>ACTION struggles to come up with a good subcommand name <paroneayea>"init" maybe, but it's just writing out example configs and etc <xd1le>is there something similar to `case` but it uses `equal?` instead of `eqv?`? Basically I want to control flow based on string values of a key. <evhan>(case x (("foo" "bar") 1)) ≈ (match x ((or "foo" "bar") 1)) <xd1le>evhan: Thanks so much! :) Sorry for the stupid question, couldn't find anything after searching for a bit. <amz3`>so the plan today is to port boolean keyword search to grf3 which a new implementation of a graphdb library <amz3`>and add some tests to at least the graphdb library <amz3`>and maybe help fix the leak bug <tohoyn_>I have a problem with compiling to CPS <wilfredh>so, I've been learning about exploring functionality with guile, making heavy use of ,d and ,a <wilfredh>is there a similar command for viewing the source of a function/macro? My google-fu has failed me <wingo>there is no nice ,foo for that <wingo>but if you use emacs and geiser <wingo>there are some library procedures that can be used to build such a thing, but it doesn't exist right now in the repl in a nice way i don't think <wingo>if you have doubts, probably a good idea to mail guile-devel with an idea of how it should work from the user's POV, and how you see it working internally <wingo>could be that you can find the right way to do it without that step tho; depends on how you like to work <wilfredh>relatedly, I've noticed that some guile functions have good comments, but no docstring <wilfredh>even though the comments are in the standard docstring formatting, with ARGUMENTS-IN-CAPS <wilfredh>is it worth me writing a patch to convert these to docstring? <wilfredh>and if so, should I send the patch to guile-devel or debbugs? <paroneayea>I don't suppose there's any nice way to write comments in any sane way to a configuration file I'm writing / pretty-printing for users <paroneayea>tried making a <komment> record type and using a custom printer <paroneayea>I forgot to display to the port in the printer, oops :) <wingo>sneek: later tell wilfredh such patches are welcome :) i think we should use texinfo as the format; there is a facility to turn texinfo in docstrings to ARGUMENTS-IN-CAPS etc <wingo>sneek: later tell wilfredh but we haven't enabled it yet <amz3`>why zip returns a list of lists instead of list of pairs? <amz3`>does it make sens to replace (zip a b) with (map cons a b) <paroneayea>amz3`: I think because zip can take more than 2 lists <paroneayea>scheme@(guile-user)> (zip '(a b c d e f g) '(z x y w) '(1 2 3 4)) <amz3`>I just benchmark srfi-41 against custom made streams, my implementation does the thing is 7s while the srfi-41 does it in 43 <amz3`>my implementation is almost 7x faster <quigonjinn>amz3`: i just run the same benchmark and it took 227s with srfi-41 and 13 with your code. But i'm using guile 2.0.12 <quigonjinn>amz3`: guessed so. My cpu is competent and it seems a great difference <amz3`>that's why I'm using 2.1.3 in the first place <wingo>channels not implemented yet :P <wingo>i want to implement some kind of atomic-op facility in guile to be able to do that <paroneayea>wingo: it's possible I'll rewrite 8sync on top of fibers, as in, drop most of 8sync's scheduling stuff, and instead focusing on "useful networking subsystems" <paroneayea>I'm still thinking about it and need to play with fibers more <paroneayea>too bad I'm so caught up in Pubstrate! TPAC is in two weeks and everything needs to work by then omigod aaaaaa <wingo>i have three talks in the next two weeks, things are nuts these days <wingo>lovely holiday in august but what a back-to-hack! <paroneayea>cwebber@oolong:~/devel/pubstrate$ ./pre-inst-env pubstrate-web configure /tmp/pubstrate-test/config.scm <paroneayea>A file already exists at this filename. Please remove it! <paroneayea>unimportant thing, but my brain is kind of anxiety'ing about all the things :)