| -module(systemd). | |
| % This is what you need to adopt systemd in erlang | |
| % | |
| % Do whatever you want license. If you want, you can take this code under terms of MIT license. | |
| -export([ready/0, reloading/0, stopping/0, watchdog/0]). | |
| -export([start_link/0]). | |
| -export([init/1, handle_info/2, terminate/2]). |
Copyright © 2016-2018 Fantasyland Institute of Learning. All rights reserved.
A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.
val square : Int => Int = x => x * x
This describes how I setup Atom for an ideal Clojure development workflow. This fixes indentation on newlines, handles parentheses, etc. The keybinding settings for enter (in keymap.cson) are important to get proper newlines with indentation at the right level. There are other helpers in init.coffee and keymap.cson that are useful for cutting, copying, pasting, deleting, and indenting Lisp expressions.
The Atom documentation is excellent. It's highly worth reading the flight manual.
| # content has to be in .config/fish/config.fish | |
| # if it does not exist, create the file | |
| setenv SSH_ENV $HOME/.ssh/environment | |
| function start_agent | |
| echo "Initializing new SSH agent ..." | |
| ssh-agent -c | sed 's/^echo/#echo/' > $SSH_ENV | |
| echo "succeeded" | |
| chmod 600 $SSH_ENV | |
| . $SSH_ENV > /dev/null |
| // | |
| // Disjunction - aka Scalaz Either | |
| // \/[A, B] is an alternative to Either[A, B] | |
| // -\/ is Left (usually represents failure by convention) | |
| // \/- is Right (usually represents success by convention) | |
| // Left or Right - which side of the Disjunction does the "-" appear? | |
| // | |
| // Prefer infix notation to express Disjunction Type v: String \/ Double | |
| // | |
| // References |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
| -module(sut). | |
| %%% Erlang 6in4 tunnel (RFC 4213) | |
| %%% | |
| %%% Not RFC compliant yet and probably buggy, but works! | |
| %%% | |
| %%% * Dependencies: | |
| %%% | |
| %%% https://github.com/msantos/procket | |
| %%% https://github.com/msantos/pkt |
