This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-02
Channels
- # asami (5)
- # aws (16)
- # babashka (41)
- # babashka-sci-dev (44)
- # beginners (157)
- # biff (3)
- # cider (1)
- # clj-commons (1)
- # cljdoc (22)
- # clojure (7)
- # clojure-dev (5)
- # clojure-europe (13)
- # clojure-nl (1)
- # clojure-uk (1)
- # clojurescript (17)
- # core-typed (13)
- # cursive (14)
- # datascript (10)
- # events (1)
- # fulcro (2)
- # graalvm (2)
- # gratitude (1)
- # jobs (3)
- # lsp (229)
- # pathom (2)
- # pedestal (3)
- # portal (53)
- # re-frame (7)
- # remote-jobs (1)
- # spacemacs (14)
- # xtdb (6)
hi, I'm trying to update some libraries in order to ultimately use Aleph TCP client in a native image for my project (@kingmob has been very helpful so far, here is the context https://clojurians.slack.com/archives/C0G922PCH/p1648437779247399)
I'm working through dependencies that use single-segment namespaces which cause issues in native image builds, especially for primitive-math
and byte-streams
. I have a PR to fix the single segment namespace in primitive-math
here https://github.com/clj-commons/primitive-math/pull/14
in this PR I also move the Java class down as well
but now I'm looking at byte-streams
and realizing there are many classes and namespaces that would need to move if I'm just putting everything under clj-commons
so does it make more sense to just move say primitive-math
namespace to primitive-math.core
and byte-streams
to byte-streams.core
and leave it at that?
only downside I see is that maybe the duplicate nses/classes are useful long term so that patches don't break compatibility. happy to know people's thoughts on this or what the standard is here
edit: thinking more I don't see a good reason not to copy ns
to ns.core
for this, so I'll do that for now