This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-20
Channels
- # aleph (4)
- # beginners (47)
- # boot (22)
- # cider (7)
- # clara (1)
- # cljs-dev (8)
- # cljsrn (21)
- # clojure (180)
- # clojure-argentina (13)
- # clojure-gamedev (1)
- # clojure-italy (5)
- # clojure-poland (4)
- # clojure-russia (17)
- # clojure-spec (19)
- # clojure-uk (33)
- # clojurescript (107)
- # cursive (61)
- # data-science (1)
- # datomic (7)
- # emacs (69)
- # euroclojure (1)
- # graphql (1)
- # hoplon (11)
- # immutant (43)
- # jobs (1)
- # leiningen (3)
- # off-topic (5)
- # om (10)
- # onyx (2)
- # parinfer (52)
- # pedestal (11)
- # re-frame (31)
- # reagent (23)
- # ring-swagger (3)
- # schema (2)
- # specter (7)
- # unrepl (9)
Do you know of any "deterministic encoding" schemes -- where the same data structure always encodes to the same byte[]? CBOR has a thing called "canonical encoding" where it sorts map keys that it serializes, but encoder support is usually broken. I'm storing payloads in a Merkle tree, and they have to always SHA to the same output, no matter who generated them
@ghadi any sort of sorted tree walk will always produce the same output
it depends on the datastructure really
naive binary tree will produce different trees for different insert orders, but the data is the same
think of it this way: how would you implement equals for your case