This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-05
Channels
- # aws (6)
- # beginners (10)
- # boot (33)
- # cider (23)
- # cljs-dev (50)
- # cljsjs (2)
- # cljsrn (10)
- # clojars (1)
- # clojure (215)
- # clojure-czech (1)
- # clojure-dev (5)
- # clojure-italy (23)
- # clojure-russia (18)
- # clojure-spec (11)
- # clojure-uk (53)
- # clojurescript (157)
- # core-async (29)
- # cursive (12)
- # data-science (15)
- # datascript (16)
- # datomic (68)
- # graphql (2)
- # jobs (5)
- # jobs-discuss (1)
- # juxt (17)
- # lein-figwheel (2)
- # luminus (3)
- # off-topic (155)
- # om (3)
- # pedestal (1)
- # portkey (1)
- # re-frame (7)
- # reagent (4)
- # ring (3)
- # ring-swagger (2)
- # rum (11)
- # unrepl (11)
- # vim (1)
- # yada (2)
@alexmiller hey Alex, can you tell if there is any progress going on about the namespace aliasing for inexistent namespaces? I remember I read something around this in past, to facilitate having alias used just for namespace resolution of keywords
currently I have a bunch of those on my code:
(create-ns 'some.deep.nested.keyword.person)
(alias 'person 'some.deep.nested.keyword.person)
this is ok on Clojure, but doesn't work for CLJS
I was wondering if would be a good idea to add something into the ns
form, to use like this:
(ns my.ns
(:alias [some.deep.nested.keyword.person :as person]))
that would work same way as require
, but without actually requiring that namespace to exist
given the reason for that namespace is just organization sake
No update right now, sorry
But I believe Rich has some idea that he has not shared with me
In general I think there is a strong preference not to make ns any more complicated