Hmm, ok those are some definite upsides. So I've been wondering protocol or multimethod, I previously used protocols, the only problem is I need to define behaviour on a per instance basis, which makes me think multimethods are the right way to do this. I was wondering if I should reach for :extend-via-metadata instead, that way I could default to a noop if the record in question is missing the key of interest for the function, but otherwise it should work?

As long as your protocol has a default implementation (for Object) that is a no-op, I think that should work...

@folcon Yeah, it works:

dev=> (defprotocol Basic :extend-via-metadata true (do-it [_]))
Basic
dev=> (extend-protocol Basic Object (do-it [_] (println "Object!")))
nil
dev=> (do-it {:a 1})
Object!
nil
dev=> (do-it (with-meta {:a 1} {`do-it (fn [_] (println "Special!"))}))
Special!
nil

Good Morning!

Morning

måning

mogge

Morn'

Awesome @seancorfield 😃... I'll have to try that approach and see if it's workable 😃...

brainwarp

I wish I could hear how people read the code they write, it would be much easier to understand

Interesting thought 😃... I wonder if reading aloud the code I write would improve readability, similar to what I sometimes do when blog writing...

yes, definitely

especially with naming things

although, if you read i or idx as Index then it might not work 🙂 I just realized because our frontend is full of buttons that are called btns

I definitely read idx as index, i / j as index keys I'd recognise, but it would not be reading, more recalling 😃

Ok, I've still not really used datafy and nav, I'm starting to work with really messy complex datastructures, is REBL still being used, or has something supplanted it? EDIT: Trying out https://github.com/djblue/portal/