This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (42)
- # alda (1)
- # beginners (11)
- # boot (24)
- # boulder-clojurians (2)
- # cider (10)
- # cljs-dev (23)
- # clojure (63)
- # clojure-czech (4)
- # clojure-japan (2)
- # clojure-russia (44)
- # clojure-sg (2)
- # clojure-switzerland (2)
- # clojurescript (135)
- # community-development (5)
- # css (4)
- # cursive (19)
- # datomic (34)
- # emacs (2)
- # events (5)
- # funcool (13)
- # hoplon (3)
- # ldnclj (43)
- # ldnproclodo (1)
- # lein-figwheel (7)
- # luminus (7)
- # off-topic (54)
- # om (115)
- # onyx (82)
- # overtone (3)
- # re-frame (6)
- # reagent (15)
- # yada (5)
Has anyone worked with sweetjs macros ? I'm wondering if they have the same capabilities as ClojureScript macros. http://sweetjs.org/
@pupeno: No idea. I always hold off on OS upgrades for 3-6 months…early adoption can be painful.
@agile_geek: I hold off for a bit too. Specially since Ruby and RVM had trouble with OS X upgrades, but Clojure seems lees immune to that.
@pupeno: agreed. Think I’ll wait a bit longer. Also my Mac is > 3 years old so not sure whether upgrading might introduce issues.
@val_waeselynck: I didn't use them, but I'm under impression they're following Scheme in that they are rule-based
from what I saw, I was under the impression that they're good for 'template-like' macros
@chedgren: not decided yet but favouring the new XPS13 (with 16GB RAM) but I want Dell to knock the bugs out of the linux drivers first so holding out for the Developer edition.
Though now I read the docs here, they also seem to provide procedural macros apart from rule macros: http://sweetjs.org/doc/main/sweet.html#rule-macros http://sweetjs.org/doc/main/sweet.html#case-macros
But that's just from reading the docs, someone who actually used it might be able to tell you more
jaen: wait what? I thought the whole point of scheme macros vs clisp macros was hygienics. And clojure having namespaced unqoute is kinda hygienic
One thing is hygiene-by-default, yes, but in IIRC in scheme you define macros "by example" by specifying the pattern of syntax you want to substitute for another, while in CL you just get AST to manipulate, like in Clojure.
I've read SICP at some point, but I've never written much scheme, so I might be misremembering, since knowledge not exercised is prone to atrophy. I think this is accurate, but if someone knows better then feel free to correct me.
Oh, so that’s how scheme’s macro works… I never understand their macros being so accustomed to that of CL’s, luckily for me Clojure’s is closer to that of CL’s.
I set it up a while ago and I dont remember having to mess with anything, if I did it probably was very straightforward
im running xmonad on debian and i would love to be able to pich-resize windows etc. but nope. multi touch is apparanetly really hard
I would be so happy if i could four finger swipe between workspaces and three finger pinch to resize windows
not sure the screen on the XPS Developer Edition is multitouch - at least not on my 2014 edition