kwonowk

javascript:(function(){
   function parseNumber(_txt){
      let txt = _txt.split(" ")[0];
      let num_clean = parseFloat(txt.replace(",",""));
      return num_clean;
   }
   function asset_name(_txt){
      let name = _txt.split(" ")[1]; 
      return name;
   }

beders

(defn create-function-call [param expr]
  "Create an sexp for calling expr with a first argument provided by a promise.
  If expr is a list (already in form suitable for a function call), insert the first argument at second position,
  otherwise turn expr into a function call expression, unless the function is an fn, which is simply returned.

  println -> (fn [param] (println param))

  (* 2)   -> (fn [param] (* param 2))
  

cheery

# I glanced through the pycket paper, saw few rules there. Ended up to doing this.

class Var(object):
    def __init__(self, name):
        self.name = name

    def __repr__(self):
        return self.name

class Lam(object):

marick

Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.

By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.

aphyr

(defrecord Retry [bindings])

(defmacro with-retry
  "It's really fucking inconvenient not being able to recur from within (catch)
  expressions. This macro wraps its body in a (loop [bindings] (try ...)).
  Provides a (retry & new bindings) form which is usable within (catch) blocks:
  when this form is returned by the body, the body will be retried with the new
  bindings."
  [initial-bindings & body]
  (assert (vector? initial-bindings))

yelouafi

// We model the call stack using a linked list of Generators
// Each Generator has a _return field pointing back to its parent

function stepGen(gen, arg) {
    const {done, value} = gen.next(arg)
    if(done) {        
        if(gen._return) {
            stepGen(gen._return, value)
        }

dustingetz

TodoMVC, with a twist! — Electric Clojure

1. it's multiplayer! 0 LOC cost
2. state is durable! (server side database) 0 LOC cost
3. See those pending spinners? We've added a server delay to demonstrate managed load states.

20220817.todomvc.mp4

Electric is a "multi tier" Clojure/Script dialect for full-stack web application development. It uses macros to let you interweave client and server code in a single .CLJC file, so you can define a full-stack frontend/backend webapp all in one place. Electric is designed for rich dynamic applications with reactive user interfaces and complex frontend/backend data sync requirements.

danielrw7

#!/bin/sh

command="${*}"
printf "Initialized REPL for `%s`\n" "$command"
printf "%s> " "$command"
read -r input
while [ "$input" != "" ];
do
    eval "$command $input"
    printf "%s> " "$command"

danneu

My efforts to port http://www.youtube.com/watch?v=f6kdp27TYZs to Clojure.

A boring function (6:22)

func boring(msg string) {
  for i := 0; ; i++ {
    fmt.Println(msg, i)
    time.Sleep(time.Second)
 }

oakes

How Clojure's documentation can leapfrog other languages

Summary

I made a documentation generator that cashes in on Clojure's dynamism. See the play-cljs docs (a ClojureScript game library) for an example of its output.

The Problem

Like many of you, I've often wondered what my final regret will be on my deathbed. My best guess came to me in a dream recently. I was walking across the charred earth of an apocalyptic future world, maneuvering around the remains of the less fortunate. I was startled to find a young girl, barely holding onto her life. She murmured something to me. I asked her to repeat it, and she said more loudly: "I...wish your Clojure projects didn't have such crappy documentation."