I had actually included a suggestion for a predefined sentinel like this in an earlier draft of my post. I scrapped that bit though, because I could not measure any consistent performance benefit on my machine, aside from not allocating a new Object each time.
Am Donnerstag, 12. Dezember 2019 12:01:52 UTC+1 schrieb Matching Socks: > > By the way, the ClojureScript version of get-in's 3-arity avoids > allocating a sentinel. Instead, it uses a predefined sentinel: > > (def ^:private lookup-sentinel (js-obj)) > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/ac887636-57c1-4dbc-83f1-89ee42700895%40googlegroups.com.
