This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-08
Channels
- # adventofcode (60)
- # announcements (3)
- # babashka (31)
- # beginners (5)
- # boot (1)
- # calva (13)
- # cider (9)
- # clj-kondo (1)
- # clojure (135)
- # clojure-italy (18)
- # clojure-nl (18)
- # clojure-spec (21)
- # clojure-uk (11)
- # clojuredesign-podcast (1)
- # clojurescript (47)
- # core-async (14)
- # emacs (7)
- # euroclojure (4)
- # fulcro (3)
- # graalvm (19)
- # off-topic (22)
- # reagent (29)
- # shadow-cljs (25)
- # vim (3)
i think this may be another native-image using util: https://github.com/liquidz/daddy
it's nice that clj-1472 is sufficiently voted -- weren't there some other relevant activities like spelling out aspects (e.g. trade-offs) of each patch alternative? i'm not succeeding in turning up the notes atm.
@sogaiu There are some TODOs here: https://github.com/lread/clj-graal-docs/tree/master/CLJ-1472#todo The most important one is probably: > cleaning all this info up and making a really readable ticket would be really helpful
But that probably includes some info on the approaches and trade-offs of the two relevant tickets?
i wonder if there are good examples of "a really readable ticket" for a somewhat analogous situation
<https://clojure.org/dev/creating_tickets> discusses how/what, but doesn't point at an example