Does anybody know if there’s a racket implementation of the influxdb http api? I need this so if there’s nothing I will have a go at it.
@jbclements I noticed this message from you from 2015 in the mailing list: https://groups.google.com/forum/#!msg/racket-users/lsZhFjUaQwE/R7GQqs9NFQAJ Did you by any chance developed an influxdb lib for racket?
@mflatt I left this comment on a commit of yours a couple weeks ago, but I’m not sure it was the best place to ask. I’m still curious, though. Is this documented anywhere, and if it isn’t, should it be? https://github.com/racket/racket/commit/c7318cab33de113ec475d7e9fd6b0ceab8fcb61d#commitcomment-29343141
@lexi.lambda You left 'only in the docs:
Was that intentional?
no, it wasn’t intentional; good catch.
(I ask because the rest of your commit doesn’t seem to acknowledge it anywhere.)
Okay cool.
Do you want to patch it or should I?
if you’re willing to push a fix, that’d be great.
@lexi.lambda As you suspect, I missed that comment/question. Now answered.
@mflatt thank you!
@lexi.lambda Okay cool, i’ve submitted a a PR: https://github.com/racket/racket/pull/2153
I’ll go ahead and merge it if you give it the okay.
@mflatt Is set! the only way to update an undefined (as provided by racket/undefined)
(Basically looking for ways to tie the knot with classes.)
(or Scala’s lazy val)
@leif Maybe I don’t understand the question, but set! isn’t necessary the only way to replace an undefined. If the undefined is in a vector, then vector-set! can replace it; if it’s in a field of a struct, then a field mutator can replace it; and so on.
Okay. So basically it can only be updated like any other value.
(Basically, I sort of wanted a…err…write once box, so to speak.)
(For use with serialize)
@leif perhaps a better way to phase it is that undefined is a value like any other
@samth fair
If Shakespeare was a racketeer he’d wonder if undefined by any other name compare as eq?