This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-10
Channels
- # asami (41)
- # babashka (24)
- # beginners (48)
- # calva (41)
- # cider (10)
- # clj-commons (20)
- # clj-kondo (2)
- # cljdoc (8)
- # clojure (131)
- # clojure-australia (4)
- # clojure-europe (17)
- # clojure-hungary (2)
- # clojure-india (2)
- # clojure-nl (3)
- # clojure-uk (1)
- # clojurescript (12)
- # community-development (6)
- # core-logic (4)
- # cursive (11)
- # datomic (22)
- # emacs (25)
- # events (1)
- # exercism (2)
- # fulcro (30)
- # helix (5)
- # honeysql (6)
- # hugsql (3)
- # integrant (12)
- # introduce-yourself (4)
- # lsp (5)
- # malli (5)
- # nextjournal (31)
- # off-topic (4)
- # pedestal (3)
- # portal (51)
- # reitit (33)
- # remote-jobs (1)
- # shadow-cljs (12)
- # sql (10)
- # vim (7)
- # xtdb (37)
not a huge thing, but did anyone ever consider adding support for functions to name
? JS has a name
property, and I was expecting name
to just access that, as the implementation for functions. eg:
(ignore reagent stuff in the error)
Indeed. It would also add to the list of distinctions between CLJ and CLJS for no good reason (meaning, you already have .-name
- you can just use it).
Asking here before filing a bug: anyone else bumped into "goog.debug.Logger is not a constructor"? My figwheel-main setup broke with this error when I upgraded CLJS 1.10.879 -> 1.10.893
oh, looks like there's a fix already: https://github.com/bhauman/figwheel-core/commit/1ac163d94edd06718d6e10df4aa944517e210420
oh, looks like there's a fix already: https://github.com/bhauman/figwheel-core/commit/1ac163d94edd06718d6e10df4aa944517e210420
@dazld we do in some case generate names to aid w/ debugging (fns inside top-levels) - there are some complexities around handling scope etc.
but there is a bigger problem which polluting the top scope if you do it at the top level