This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-18
Channels
- # announcements (2)
- # beginners (95)
- # cider (2)
- # cljdoc (5)
- # cljs-dev (11)
- # cljsrn (2)
- # clojure (12)
- # clojure-spec (11)
- # clojure-uk (3)
- # clojurescript (27)
- # code-reviews (4)
- # cursive (9)
- # data-science (1)
- # datomic (1)
- # emacs (7)
- # fulcro (13)
- # graalvm (28)
- # graphql (6)
- # nrepl (6)
- # off-topic (13)
- # re-frame (3)
- # rewrite-clj (2)
- # shadow-cljs (29)
- # spacemacs (1)
- # sql (4)
- # tools-deps (8)
- # vim (20)
- # yada (7)
I think we don’t implement IMeta for arbitrary objects because it would require either mutating the object or doing some sort of copy
Right. I had suggested that a revision to macroexpansion logic couldn't arbitrarily put meta on the result of macroexpansion (in other words convey, induce, whatever term). Mike is right in that you could force the issue. But you definitely wouldn't want to. Nor does it seem either necessary, and the whole idea seems at odds with Clojure's behavior.
In some sense, one odd aspect of the hinting failure is that it only happens because we happen to have a macro defined for aget
.
It seems like currently most optimisations that are built with type inference are operating with primitive types e.g. string boolean number, would it make sense to include core data types as well?
To be fair there's also 'array and 'seq
https://clojure.atlassian.net/browse/CLJS-3132 is an example of optimizations surrounding cljs.core/Keyword
and cljs.core/Symbol
I was thinking about checked if, right now compiler is looking for constant values, boolean and seq
What is 'clj tag for btw?