IRC channel logs


back to list of logs

***profan_ is now known as profan
<ArneBab_>davexunit: after fixing my X11, your wrapper now shows a window, once there was an image inside.
<davexunit>ArneBab: thanks for testing! glad it worked.
<ArneBab_>davexunit: I also got a transparent image a few times
<ArneBab_>transparent window
<amz3>héllo :)
***rjungemann_ is now known as rjungemann
<OrangeShark>hello everyone
<davexunit>ArneBab_: okay. I don't know what would cause that.
<davexunit>the fact that it works sometimes is good enough for me, for now.
<ArneBab_>that’s much more than I could provide for a guile program → yay!
<davexunit>unboxed float comparisons have landed in master.
<daviid>davexunit: congrat!
<civodul>neat, great job davexunit!
<davexunit>thanks civodul
<davexunit>I hope it will benefit people besides myself ;)
<paroneayea>davexunit: YAY
<davexunit>hey paroneayea
<davexunit>got commit access too. :)
<ArneBab_>davexunit: nice!
<paroneayea>davexunit: I'm assuming you won't be bothered by me adding a guile-sjson package based on your (ice-9 json) work and packaging it up in guix!
<davexunit>paroneayea: not at all
<paroneayea>you might be more bothered that I'm going to switch '(@ (key . val) (key2 . val2)) to '(@ (key val) (key2 val2)) :)
<davexunit>apologies for not getting it upstreamed for over a year
<paroneayea>but, I couldn't easily work with some of the pretty printed stuff because I have so many associative arrays bundling lists
<davexunit>I can't remember the specifics of syntactic choices enough right now to know if I like or dislike that. :)
<davexunit>do what works ;)
<paroneayea>cool :)
<paroneayea>I'll also add my pile of sjson utilities I built for pubstrate
<paroneayea>so we'll have an sjson-pprint and friends
<paroneayea>as well as a few utilities for slicing and dicing them
<wingo>great work davexunit on the f64 stuff :)
<davexunit>thanks for all the help wingo!
<davexunit>it's a much bigger project of course, but something like unboxed struct fields would be the next thing I'm interested in seeing.
<davexunit>I know you have ideas about what the right thing is there.
<davexunit>and using the existing structs seems to not be the right thing.
<paroneayea>davexunit: Should I leave your copyright as FSF and add a comment attributing you for sjson.scm or switch it to David Thompson since it's not part of Guile? Either would be fine I think since I did borrow it from a guile submission
<davexunit>paroneayea: attribution to "david thompson" would be my preference
<davexunit>since it never made it upstream
<holomorph>hopefully it does someday!
<paroneayea>davexunit: but leave copyright as fsf or switch that line too?
<davexunit>you can just leave it as-is I guess
<davexunit>fsf-only attribution
<paroneayea>sorry, I think it's getting confusing because attribution and copyright are intermingled here, but also kind of different
<paroneayea>it sounds like your preference would be a line like this, if that's how my name is too:
<paroneayea>;;;; Copyright © 2015 David Thompson <>
<paroneayea>sorry asking got so convoluted :)
<davexunit>no worries :)
<paroneayea>davexunit: got a sec?
<paroneayea>davexunit: json-object-ref or json-ref ?
<paroneayea>for '(@ ("foo" "bar"))
<paroneayea>same for json-fold, json-map, etc
<paroneayea>or json-object-fold json-object-map
<davexunit>hmm, dunno
<paroneayea>I used to use json-alist-foo
<paroneayea>but now I switched it to json-object-foo
<paroneayea>but now I'm thinking, do I even need that middle part
<davexunit>I don't know if I'd ever actually use those procedures
<paroneayea>davexunit: you might not, but I use them a lot
<davexunit>because pulling data out of a nested structure is wasteful
<paroneayea>davexunit: but if you've imported some json, wouldn't you want to pull out data?
<davexunit>I would iteratre over the results and transform them into things with real types
<davexunit>an array of json objects I would map to a list of some record type
<paroneayea>ok, well, sometimes you're just hacking on some json you pulled in :)
<paroneayea>or I am
<davexunit>but I guess I would prefer object-ref because there are also arrays that could be ref'd
<paroneayea>ok, I'll keep json-object-ref
<paroneayea>I agree that usually you want to transform into some intermediate data
<paroneayea>but sometimes it's not worth it, or sometimes you're working on a json heavy api
<davexunit>on json-ref could be polymorpic
<davexunit>if the list begins with '@ it's an object ref, otherwise list-ref
<paroneayea>I'm all for generic methods, but I have a hard time imagining what time I'd use that :)
<paroneayea>json-ref gives that impression
<paroneayea>whereas json-object-ref is clear
<paroneayea>so that's a good argument for json-object-ref
<paroneayea>thanks for talking it through davexunit
<paroneayea>davexunit: you might not think you'll use these yet, but some day you'll hack a json api and you'll be like, oh json-object-ref! so useful ;)
<paroneayea>anyway thanks again for the feedback
<paroneayea>I need to update the template I've been using so it doesn't install to just either guile 2.0 or 2.2
<paroneayea>what's a good package to look at?
<paroneayea>guix? haunt? ?
<paroneayea>Haunt has a nice commit showing how
<paroneayea>I'll follow that :)
<amz3`>my pod was disconnect :(
<amz3`>my pod was disconnected :(