towards enlightenment
‘It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts.’
(ns miracle.tools.save | |
(:require [clojure.walk :refer [postwalk]])) | |
;; usage | |
;; | |
;; (save) or (save :whatever) somewhere in a function to save all the local | |
;; bindings at that point in time. | |
;; | |
;; (save-func ...) where ... is the body of your functions (e.g. (defn hej [a] | |
;; (save-func (let [b 5] (+ a b))))) |
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:
; A REPL-based, annotated Seesaw tutorial | |
; Please visit https://github.com/daveray/seesaw for more info | |
; | |
; This is a very basic intro to Seesaw, a Clojure UI toolkit. It covers | |
; Seesaw's basic features and philosophy, but only scratches the surface | |
; of what's available. It only assumes knowledge of Clojure. No Swing or | |
; Java experience is needed. | |
; | |
; This material was first presented in a talk at @CraftsmanGuild in | |
; Ann Arbor, MI. |
;;;; pretty-literals.lisp - pretty hash table & vector literal syntax | |
;;;; inspired by and uses code from http://frank.kank.net/essays/hash.html | |
(in-package #:pretty-literals) | |
;; vector literal syntax using brackets | |
(set-macro-character #\[ | |
(lambda (str char) | |
(declare (ignore char)) | |
(let ((*readtable* (copy-readtable *readtable* nil)) |
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this:
There are 3 primary ways to pass data into functions: move, copy, or borrow (aka a reference). Since mutability is inherently intertwined with data passing (this function can borrow my data, but only if they promise not to mess with it), we end up with 6 distinct combinations.
Every language has its own level of support and take on these semantics: