This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-16
Channels
- # admin-announcements (9)
- # beginners (112)
- # boot (223)
- # cbus (10)
- # cider (19)
- # clara (2)
- # cljs-dev (81)
- # cljsjs (3)
- # cljsrn (45)
- # clojure (239)
- # clojure-conj (12)
- # clojure-poland (2)
- # clojure-russia (56)
- # clojure-taiwan (1)
- # clojurescript (57)
- # cursive (28)
- # datomic (5)
- # events (14)
- # immutant (1)
- # jobs (1)
- # ldnclj (8)
- # off-topic (28)
- # om (80)
- # onyx (121)
- # re-frame (10)
- # sneer-br (1)
- # spacemacs (40)
- # yada (44)
And I haven't needed a debugger in Clojure at all-- just test small snippets in REPL and paste them into source file. If something doesn't work, then I just use println/console.log
@johanatan: That's my experience too. I never use a debugger in Clojure, although it's possible now. I do use it in Ruby though, binding.pry.
To answer your original question though, foo(*v) is the equivalent of JS apply (it expands the array v to match the args accepted by foo)
What is a good name for a function that calculated the price after a possible reduction
@borkdude discount-price ?
@nilbus: @agile_geek I didn't tell you this was Ruby, so _ is more appropriate
@nimbus @borkdude as discount is a verb as well as a noun I thought discount the price i.e. discount_price was slightly better than price_after_discount which sounds like a field not a function? Happy to be contradicted tho
sounds good
could have used discounted_price as well