It’s not so easy to get *ns* string in ClojureScript as you might expect but here is a tip.
It is impossible to get *ns* string at run-time in ClojureScript (except in self-hosted ClojureScript) but it can be accessed at compile-time only. So you have to use a macro to get it as the following example.
I came up with this idea in the course of implementing set-ns-blacklist! and set-ns-whitelist! (https://github.com/philoskim/debux#debux-config) in my debux library.
An experimental change for fast Clojure REPL startup:
java -jar clojure-1.8.0-fast.jarThe code used to create this JAR is on GitHub.
What's it doing?
It is:
| # This version: | |
| # brings WiFi in from the Huawei adapter on eth1 | |
| # pushes WiFi out from the built in adapter on wlan0 | |
| # sets up an ip address on 192.168.5.2 to ssh into from another computer | |
| ################################################## | |
| # Update | |
| # | |
| #sudo apt-get update | |
| #sudo apt-get -qq upgrade |
| ; http://stackoverflow.com/questions/31269170/event-count-at-certain-time-interval-in-riemann | |
| (let [email (mailer {:host "localhost" | |
| :port 1025 | |
| :from "abc@gmail.com"})] | |
| (streams | |
| (where (and (service "system_log") | |
| (description "IE") | |
| (not (expired? event))) | |
| ; we are interested in the event count, so let's fix to :metric 1 |
| (ns favila.async-util | |
| "Some missing pieces of core.async. | |
| as-transducer: Make a transducer function easily without Clojure 1.7. | |
| go-pipe: async/pipe, but returns the go-loop. | |
| fast-pipeline-blocking: faster than async/pipeline-blocking, but unordered results. | |
| blocking-consumer: consume a channel with multiple worker threads." | |
| (:require [clojure.core.async :as async | |
| :refer [go go-loop <! >! <!! >!! close! take! put! chan]])) |
| (ns foami.core | |
| "FOreign Asynchronous Mechanism Interop" | |
| (:require [clojure.core.async :as async])) | |
| (defn put! | |
| "Takes a `ch`, a `msg`, a single arg function that when passed `true` enables backpressure | |
| and when passed `false` disables it, and a no-arg function which, when invoked, closes the | |
| upstream source." | |
| [ch msg backpressure! close!] | |
| (let [status (atom :sending] |
| (comment ; Fun with transducers, v2 | |
| ;; Still haven't found a brief + approachable overview of Clojure 1.7's new | |
| ;; transducers in the particular way I would have preferred myself - so here goes: | |
| ;;;; Definitions | |
| ;; Looking at the `reduce` docstring, we can define a 'reducing-fn' as: | |
| (fn reducing-fn ([]) ([accumulation next-input])) -> new-accumulation | |
| ;; (The `[]` arity is actually optional; it's only used when calling | |
| ;; `reduce` w/o an init-accumulator). |
Simply put, destructuring in Clojure is a way extract values from a datastructure and bind them to symbols, without having to explicitly traverse the datstructure. It allows for elegant and concise Clojure code.
