This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-06
Channels
- # aleph (15)
- # beginners (40)
- # boot (14)
- # cider (90)
- # cljs-dev (132)
- # cljsrn (25)
- # clojars (7)
- # clojure (188)
- # clojure-chicago (4)
- # clojure-dusseldorf (1)
- # clojure-greece (9)
- # clojure-italy (43)
- # clojure-russia (16)
- # clojure-sg (7)
- # clojure-spec (39)
- # clojure-uk (81)
- # clojurescript (170)
- # component (5)
- # core-async (7)
- # cursive (49)
- # data-science (65)
- # datascript (3)
- # datomic (27)
- # graphql (3)
- # hoplon (4)
- # instaparse (56)
- # klipse (129)
- # leiningen (1)
- # lumo (28)
- # off-topic (4)
- # om (15)
- # onyx (54)
- # overtone (7)
- # pedestal (7)
- # re-frame (9)
- # reagent (72)
- # ring (33)
- # ring-swagger (2)
- # spacemacs (1)
- # untangled (19)
- # vim (2)
- # yada (12)
so one use-case in which it is pretty groovy to have access to a "compile" function at run-time is for something like a differential equation solver
where you might want to allow your user to solve differential equations with arbitrary right-hand sides
but you'd like to parse the user input and compile it into machine-code because it's evaluated many times in the inner-loop of your solver
in c++ it's basically impossible for us to get this behavior - the user input becomes like some AST objects that we walk and evaluate at run-time, so we have to tell our users "yeah, we provide this way for you to enter arbitrary functions, but you shouldn't really use it for performance reasons"