@gfredericks: You are the man for doing this - https://github.com/google/closure-library/pull/741

@xcthulhu: I can't resist a good arithmetic bug

Okay I'm going to have to try to fix one now too. Google Closure doesn't handle UTF-8 properly, so every time I've tried to use it for taking SHA256 of unicode it's been borked.

Also I was curious how to speed up division, the way GMP does it is by divide and conquer reducing the problem to Möller-Granlund division: https://github.com/SaberMod/gnu-gmp/blob/faf7424576910eca222b0ddaea6bbe490e10e70e/mpn/generic/dcpi1_div_qr.c

(s/def ::basically-an-integer
  (s/or :exact integer?
        :inexact #(and (number? %)
                       (zero? (- (int %) %)))))
(s/def ::basically-a-positive-integer
  (s/and ::basically-an-integer pos?))

user> (s/conform ::basically-an-integer 1.0)
;; => [:inexact 1.0]
user> (s/conform ::basically-a-positive-integer 1.0)
;; => ClassCastException   [trace missing]

@alexmiller: realizing that there hasn't been an alpha release in nearly a month makes me wonder: would you say that spec has pretty much stabilized at this point? Not that I'm requesting any sort of commitment to that, of course; just curious what your sense is.

no

Rich has just been busy/ooo

We have a ton of stuff queued up :)

Makes sense, thanks! Looking forward to checking it out 😄

@calvis Rich has suggested having both a flowing and non-flowing version of and and I think it’s likely that will eventually happen (probably and-> for flowing and and for non-flowing, although that changes the current meaning of and)

@alexmiller: yeah, that would be helpful. can’t really keep track which of my specs are or’s and which aren't

one option here is to use s/conformer in ::basically-a-positive-integer to unwrap

(s/def ::basically-a-positive-integer (s/and ::basically-an-integer (s/conformer val) pos?))