This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-21
Channels
- # beginners (5)
- # boot (15)
- # capetown (1)
- # chestnut (2)
- # cljs-dev (9)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (190)
- # clojure-brasil (2)
- # clojure-greece (14)
- # clojure-italy (3)
- # clojure-poland (8)
- # clojure-romania (1)
- # clojure-russia (2)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (98)
- # clojure-ukraine (2)
- # clojurescript (65)
- # clojurex (1)
- # core-async (16)
- # cursive (16)
- # datomic (3)
- # defnpodcast (7)
- # emacs (11)
- # funcool (2)
- # hoplon (16)
- # jobs (1)
- # leiningen (4)
- # lumo (9)
- # off-topic (2)
- # om (1)
- # other-languages (1)
- # protorepl (1)
- # re-frame (50)
- # reagent (16)
- # reitit (32)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (73)
- # spacemacs (36)
- # specter (21)
- # sql (6)
- # unrepl (107)
- # untangled (4)
Has there been discussion around a compiler option that could strip docstrings from output (perhaps useful when :advanced
and trying to reduce output size)?
My motivation for asking is the effect https://dev.clojure.org/jira/browse/CLJS-2407 has on code size
@rarous pretty sure they get compiled into comments, docstring are not runtime meta, just compiler meta
I grepped for the docstring for cljs.core/map
and found it in builds/out-adv/core-advanced-test.js
, and mistakenly assumed all were appearing. I can see that others like cljs.core/first
are present, but not cljs.core/iterate
. I'll see if I can sort out what the difference is.
Perhaps it is the result of applying var
to some of those Vars or some other suitable explanation.