This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
At first blush, it looks like
realized? can be made to work for lazy seqs by simply checking if
nil. I may dig further to see if this really holds true or if I’m missing something subtle. (Patch: https://gist.github.com/mfikes/ef1b535ab41d1e706a5c)
I’ll try a simple patch for
realized? for discussion. If it is no good, we can reject / decline it. http://dev.clojure.org/jira/browse/CLJS-1531
are all these arities defined for performance reasons? https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L427-L453
@anmonteiro: A guess: It makes things consistent with Clojure, which can have only 20 positional arguments.
@mfikes: that makes sense, but I was wondering if there's also any performance implication
another example: David defined several arities in Om's
@dnolen A few core predicates like
cloneable? delegate directly to
satisfies? and lack
^boolean, while others like
indexed? are hinted. Is there an interest in patches for these, or would it be (premature optimization) noise you'd rather not deal with?