This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-09
Channels
- # announcements (1)
- # arachne (1)
- # beginners (34)
- # boot (5)
- # calva (68)
- # cider (34)
- # cljs-dev (1)
- # clojure (36)
- # clojure-italy (8)
- # clojure-spec (16)
- # clojure-uk (58)
- # clojurescript (29)
- # cursive (2)
- # datascript (9)
- # datomic (3)
- # emacs (10)
- # figwheel (1)
- # figwheel-main (11)
- # fulcro (33)
- # luminus (5)
- # mount (2)
- # nrepl (42)
- # off-topic (3)
- # other-languages (2)
- # parinfer (3)
- # perun (4)
- # prelude (3)
- # re-frame (6)
- # reagent (5)
- # shadow-cljs (23)
- # sql (37)
- # testing (1)
I don’t think that works anymore in modern jvms
Or has no effect
-J-Xverify:none
still seems to make a difference on OpenJDK 11 vs OpenJDK 8. The -client
and tiered stuff, not so much.
I thought they didn’t allow you to turn off the verifier anymore, but been a while since I looked at it
In any case, don’t turn off the verifier :)
> (per that wiki page -- but see the caveats around that) 🙂
seeing this error running an old version of a library (liberator 0.12.2) on java 11 using the clojure cli:
CompilerException java.lang.ClassNotFoundException: javax.xml.ws.ProtocolException, compiling:(liberator/conneg.clj:1:1)
is there a workaround for this? I believe it's a general issue running old libraries on java 11, and the answer is to add the dependency using --add-modules
but I'm not sure how to do that. also, it's a regression test so I can't upgrade the liberator libraryI think in Java 11 the better solution is to add the javax jaxb dependencies (available on Maven).
how do people typically deal with missing values NA or NaN type values when doing data science type stuff in clojure? Is using nil or ##NaN obviously better?
Is there a best practice for namespaced keys in nested maps? e.g. I have this structure with namespaced keys but see it is rather verbose:
{:document/entities
{:entity/extracted ...
:entity/tagged ... }}
@cbowdon you can do this to save a little repetition:
{:document/entities
#:entity{:extracted []
:tagged [] }}
Thanks - sorry I should have said I’m aware of that syntax but even then it doubles up on entity/entities in this example.
I'm not 100% what you mean, do you mean you want the :entity
keyword qualifier somehow inferred from it being below :document/entities
in the tree?
I think a lot of the qualified keyword stuff is a place where verbosity has been hard to avoid in my experience
@cbowdon If you want to reduce the verbosity in your code, I'd look at using tagged literals. I put together an example of doing that https://gist.github.com/shaunparker/c89ac63cba98d05d9586a837654b1c1e. If you have clojure installed locally you can run clojure -Sdeps '{:deps {keyword-tagged-literal-ex {:git/url "
Not quite what I’m looking for. I want to ask.. is this map from this particular namespace
just to point out, maps cannot be namespaced. there's a shorthand for when all of the keys share the same namespace but this is a property of those keys and not the map
however, could you walk over things and collapse maps whose entries are keywords which all share the same namespace into a single entry?
(-> #:step{:name 'some-name} first key namespace)
if you can count on the map's key entries to all have the same NS