mourjo

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Commentary                                                            ;;
;;                                                                       ;;
;; The goal for writing this started with the idea to have tests run in  ;;
;; parallel using the leiningen plugin eftest                            ;;
;; https://github.com/weavejester/eftest.                                ;;
;;                                                                       ;;
;; With tests using with-redefs, it was not possible to run them in      ;;
;; parallel if they were changing the root binding of the same           ;;
;; vars. Here, we are binding the root of the var to one function that   ;;

leonoel

(ns asyncawait
  (:refer-clojure :exclude [await])
  (:require [cloroutine.core :refer [cr]]))

(defmacro async [& body]
  `(js/Promise. (fn [s# f#]
                  (spawn (cr {await thunk}
                           (try (s# (do ~@body))
                                (catch :default e# (f# e#))))))))

lilactown

# Add these to your .bash_profile / .zshrc / etc.

# Starts a Clojure repl
function rebel-clj() {
  clojure -Sdeps "{:deps {com.bhauman/rebel-readline {:mvn/version \"0.1.4\"} $@}}" -m rebel-readline.main
}

# Starts a browser REPL
function rebel-cljs() {
  clojure -Sdeps "{:deps {com.bhauman/figwheel-main {:mvn/version \"0.1.7\"} com.bhauman/rebel-readline-cljs {:mvn/version \"0.1.4\"} $@}}" -m figwheel.main

mfikes

The goal is to have the spec-related code conditionally elided from the below for prod builds:

(ns my-app.core
  (:require [clojure.spec.alpha :as s]
            [my-app.config :as config]))

(defn new-machine
  [opts]

stuarthalloway

;; I think it would be a mistake to introduce temporal coupling to prevent typos.

;; The example program below lets you identify "missing" keys specs at
;; the time and place of your choosing, and then handle them as you
;; deem appropriate, without imposing those decisions on other
;; users of spec.

(require '[clojure.spec.alpha :as s]
         '[clojure.set :as set])

pesterhazy

Reagent state bidi input

This Gist demonstrates problems with synchronizing input fields in reagent.

Shows how to bind an atom to a remote state asychronously and bidirectionally

reborg

Rich Already Answered That!

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 link in the table of content jumps at the copy of the answer on this page.
• The link on the answer itself points back at the original post.

Table of Content

pesterhazy

;; in your project definition
;; [cljsjs/react-select "1.0.0-rc.1" :exclusions [cljsjs/react]]

;; See react-select documentation: https://github.com/JedWatson/react-select

(ns example.select
  (:require [reagent.core :as r]
            [cljsjs.react-select]))

(defn select

briansunter

How can we extend functionality in Clojure without modifying the orignal source?

Let's say we want to computer the area of some Shape types like Square and Circle

We have multiple shapes all of which have an area function

We may have some function called sum-areas that takes a list of Shape , calls area on each of them, and sums them up. We don't have access to the original source, but want the ability to add new shapes.

pesterhazy

#!/usr/bin/env python
#
# lumo-deps: lumo with JavaScript or ClojureScript dependencies
#
# Synopsis:
#
# lumo-deps [-c clojure-dep] [-j javascript-dep] [-- lumo-opt1 lumo-opt2 ...]
#
# Starts a lumo session with ClojureScript or JavaScript dependencies loaded.
#