This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-12
Channels
- # adventofcode (6)
- # announcements (10)
- # beginners (70)
- # boot (55)
- # calva (15)
- # cljs-dev (18)
- # clojure (32)
- # clojure-europe (4)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-uk (6)
- # clojurescript (14)
- # cursive (11)
- # datomic (31)
- # figwheel-main (7)
- # fulcro (1)
- # incanter (1)
- # jobs-discuss (3)
- # juxt (1)
- # off-topic (17)
- # onyx (5)
- # pathom (3)
- # pedestal (2)
- # quil (20)
- # re-frame (6)
- # reitit (1)
- # ring (2)
- # rum (5)
- # shadow-cljs (73)
- # spacemacs (5)
- # tools-deps (11)
- # uncomplicate (1)
- # unrepl (1)
- # yada (11)
What determines the execution order of events? I know dispatch has no order so {dispach-n [[:a][:b]]}
might result in a or b happening in any order. But if a and by both dispatch
a-->c
b-->d
I'm not sure if i can expect a
and b
to have finished before c
. So lets say c
is a reg-fx that increments a counter by 1. and b is a normal reg-event-fx, but it dispatches to a reg-fx d
that decrements the counter by 1. Does anything in reframe order them or is both orders: c,d
and d,c
possible? So at any point, the counter could be -1, 0, 1 (assuming it started at 0).@brewmasterv events are handled FIFO
So {dispach-n [[:a][:b]]}
will mean that [:a]
is fully processed before [:b]
is processed
@mikethompson ah right, i meant if if the effects map is {:a something :b something}
There is no ordering to the processing of effects