This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-08
Channels
- # aleph (11)
- # arachne (7)
- # aws (1)
- # bangalore-clj (4)
- # beginners (24)
- # boot (128)
- # bristol-clojurians (23)
- # cider (1)
- # cljs-dev (43)
- # cljsrn (6)
- # clojure (178)
- # clojure-austin (3)
- # clojure-chicago (1)
- # clojure-dusseldorf (14)
- # clojure-finland (15)
- # clojure-france (6)
- # clojure-italy (18)
- # clojure-portugal (2)
- # clojure-russia (67)
- # clojure-spec (148)
- # clojure-uk (55)
- # clojurescript (199)
- # core-async (4)
- # cursive (18)
- # datascript (5)
- # datomic (120)
- # devcards (3)
- # dirac (53)
- # emacs (11)
- # events (3)
- # gsoc (7)
- # jobs (1)
- # lein-figwheel (25)
- # leiningen (5)
- # lumo (12)
- # off-topic (29)
- # om (174)
- # om-next (2)
- # onyx (7)
- # perun (10)
- # protorepl (6)
- # re-frame (12)
- # remote-jobs (1)
- # ring (19)
- # ring-swagger (25)
- # rum (6)
- # spacemacs (13)
- # sql (3)
- # untangled (88)
- # yada (7)
I noticed the application says, Clojure wasn't accepted in 2015 in application.md
, maybe that's a typo, because it was.
should be 2016
I'm thinking of a couple of ideas, but I'm not entirely sure if they're feasible GSoC projects. So maybe experienced Clojure programmers can let me know what you think: - SMT based verification tool in Clojure/wrapper around Z3. - Memory/performance profiler. (I'm not sure of what's the state of the art in this space in Clojure, I'm thinking of something along the lines of https://blog.golang.org/profiling-go-programs)
@akhileshs Thanks for catching that error. This evenging, I’m planning on putting up the full application and profile I am planning on submitting.