This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-19
Channels
- # aws (2)
- # beginners (135)
- # boot (20)
- # chestnut (7)
- # cider (18)
- # clara (5)
- # cljs-dev (50)
- # cljsrn (30)
- # clojure (252)
- # clojure-italy (9)
- # clojure-losangeles (5)
- # clojure-russia (8)
- # clojure-spec (33)
- # clojure-uk (5)
- # clojurescript (32)
- # clr (4)
- # cursive (5)
- # data-science (1)
- # datascript (1)
- # datomic (40)
- # emacs (1)
- # fulcro (18)
- # graphql (11)
- # hoplon (3)
- # lein-figwheel (2)
- # lumo (47)
- # off-topic (2)
- # om-next (3)
- # onyx (10)
- # pedestal (22)
- # protorepl (6)
- # re-frame (7)
- # reagent (38)
- # ring (1)
- # ring-swagger (5)
- # rum (3)
- # spacemacs (19)
- # specter (5)
- # vim (13)
- # yada (16)
@michaeldrogalis in metamorphic, can you create multiple runtimes - e.g. a runtime for each of several core.async channels you might have?
The runtime is almost functionally pure. There’s an atom that’s a bit tricky to get rid of. Possible though.
So someday you’ll be able to fork the runtime if you wanted to and take it in two different directions.
But, yeah. The runtime isn’t a singleton, so create as many rt’s as you’d like.
and as for core.async, or really any other async integration - event history is up to you to feed metamorphic?
Yeah. All it knows is rt/process-event
. Feed it however you’d like.
Awesome, let us know how you go. Thanks!