This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-28
Channels
- # bangalore-clj (1)
- # beginners (67)
- # braveandtrue (179)
- # cider (28)
- # cljdoc (1)
- # clojure (132)
- # clojure-conj (3)
- # clojure-dev (1)
- # clojure-finland (6)
- # clojure-nl (2)
- # clojure-russia (6)
- # clojure-spec (19)
- # clojure-uk (62)
- # clojurescript (90)
- # clojutre (5)
- # component (2)
- # cursive (30)
- # data-science (1)
- # datomic (42)
- # duct (9)
- # emacs (1)
- # figwheel-main (158)
- # fulcro (57)
- # funcool (3)
- # hoplon (1)
- # jobs (17)
- # mount (38)
- # off-topic (15)
- # re-frame (53)
- # remote-jobs (2)
- # schema (11)
- # shadow-cljs (299)
- # spacemacs (25)
- # specter (2)
- # tools-deps (54)
- # vim (11)
- # yada (6)
Cool, I've been reading up on the wast semantics. Thinking about how to build a cljs-subset->wast dsl.
@benzap do you have any recommendations on how you'd go about implementing a wast dsl in clj/s?
But I also tried just defining most of the functions in the spec as first class functions, emitting strings, while closing over any strings passed in as parameters, and that seems to compose wast forms pretty easily too
Then it should just be a matter of defining functions over those string fns that translate more clojurey fn semantics to the wast
I kind of want to do what I did with fif, where everything is expressed as EDN symbols, but i'm worried they'll add something to later specs that will break that particular method
so yeah, I might go the string route for WASM, but for an intermediate, i'll make it an EDN-based language, so it can be used as a clojure DSL