This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-02
Channels
- # admin-announcements (9)
- # alda (21)
- # announcements (1)
- # beginners (68)
- # boot (241)
- # braid-chat (18)
- # cider (32)
- # cljs-dev (4)
- # cljsrn (11)
- # clojure (60)
- # clojure-dusseldorf (1)
- # clojure-germany (1)
- # clojure-poland (212)
- # clojure-russia (64)
- # clojure-sg (10)
- # clojurescript (212)
- # core-async (1)
- # css (14)
- # datomic (1)
- # emacs (9)
- # funcool (2)
- # hoplon (18)
- # jobs (1)
- # ldnclj (1)
- # lein-figwheel (5)
- # leiningen (3)
- # om (190)
- # onyx (46)
- # parinfer (13)
- # proton (3)
- # re-frame (7)
- # reagent (10)
- # ring-swagger (2)
- # slack-help (3)
- # specter (1)
- # yada (31)
Hi I'm really keen to help out with Alda (I'm passionate about Clojure and about music..)
I saw this issue https://github.com/alda-lang/alda/issues/160 which sounds pretty straightforward to pick up and will be (hopefully!) an easy way to help out while I get to know the codebase - is it a case of changing most/all def
s to defonce
? If so is there anything rigorous I can do to test that it's worked beyond leaving it on for a few hours?
we have a bunch of things (mostly defined as dynamic vars) that are reused that should probably be defonce
'd instead of def
wasn't familiar enough with the inner workings to know whether it would be safe to change those
one way that i've typically been able to reproduce the issue is to start a server and play around with it, then shut my laptop and come back later and re-open it and interact with the same server