| ;;=============== play with flow ============== | |
| (require '[clojure.core.async :as async] | |
| '[clojure.core.async.flow :as flow] | |
| '[clojure.pprint :as pp] | |
| '[clojure.datafy :as d] | |
| '[clojure.walk :as w]) | |
| (set! *warn-on-reflection* true) | |
| (defn monitoring [{:keys [report-chan error-chan]}] |
| ;; let's say you want to perform an action only when a state is true and returns true/false depending on the action success | |
| ;; typically I would write | |
| (if @open ; check state | |
| (do | |
| (.put q bytes) ; action | |
| true) | |
| false) | |
| ;; or |
(updated versions of this document, plus more, live here)
This will show you how to get Guix running on WSL2.
We're going to go as "minimal" as possible, without starting off one of the readily available WSL2 distros.
Parts of this guide should help with understanding how to set up any custom distro on WSL, not just Guix.
Disclaimer: I'm a Guix nOOb! (hence going through the trouble of installing it on WSL2)
In the wake of the virus that-must-not-be-named (which most people misname anyway), it seems like everyone and their cat has posted some sort of opinion or how-to on making remote work, work. This is a good thing! Working remotely, particularly full-time, is hard! I've done it for my entire career (aside from an odd 14 month office period in the middle that we shall not speak of), but more relevantly, for the past two years I've been responsible for building, managing, and enabling an entirely remote team, distributed across nine timezones. Remote teams don't just happen by installing Slack and telling everyone to work on their couch: they require a lot of effort to do correctly and efficiently. But, done right, it can be a massive multiplier on your team efficiency and flexibility.
Here's how we do it. I'm going to attempt to structure this post more towards management than engineering, and so I apologize in advance if I assume terminology or knowledge which
| public static <T> Stream<T> inCompletionOrder(Collection<CompletableFuture<T>> futures) { | |
| BlockingQueue<CompletableFuture<T>> queue = new LinkedBlockingQueue<>(); | |
| for (CompletableFuture<T> future: futures) { | |
| future.whenComplete((value,exception) -> queue.add(future)); | |
| } | |
| return Stream.generate(noException(queue::take)) | |
| .map(CompletableFuture::join) | |
| .limit(futures.size()); | |
| } |
| (require '[clojure.spec.gen.alpha :as sgen]) | |
| ;; original | |
| (defn multimethod-selector | |
| "Returns a generator that picks one dispatch value from the known | |
| dispatch values of a multimethod. Defers the lookup of dispatch | |
| values until sampling time, so any defmethods evaluated after the | |
| generator is created may still be selected." | |
| [s] | |
| #(sgen/bind |
| (ns yourproject.yourns | |
| (:require [clojure.java.io :as io])) | |
| (defn delete-directory-recursive | |
| "Recursively delete a directory." | |
| [^java.io.File file] | |
| ;; when `file` is a directory, list its entries and call this | |
| ;; function with each entry. can't `recur` here as it's not a tail | |
| ;; position, sadly. could cause a stack overflow for many entries? | |
| ;; thanks to @nikolavojicic for the idea to use `run!` instead of |
A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.
How to use:
| ;; the SET game in clojure.spec | |
| ;; inspired by https://github.com/jgrodziski/set-game | |
| (require '[clojure.spec :as s]) | |
| (s/def ::shape #{:oval :diamond :squiggle}) | |
| (s/def ::color #{:red :purple :green}) | |
| (s/def ::value #{1 2 3}) | |
| (s/def ::shading #{:solid :striped :outline}) | |
| (s/def ::card (s/keys :req [::shape ::color ::value ::shading])) |
| ; Learn Datalog Today (http://www.learndatalogtoday.org) is a great resource for | |
| ; reading but its interactive query interface is broken. Below is how we can | |
| ; load the same data into a Clojure REPL and play with it using DataScript. | |
| ; After running the code below, many/most/all? of the queries on Learn Datalog | |
| ; Today should be functional. | |
| ; | |
| ; Create a new lein project, add `[datascript "0.15.0"]` to `project.clj`'s | |
| ; `dependencies`, run `lein deps && lein repl` and copy-paste the following in | |
| ; chunks, inspecting the outputs as needed. |