moleike

This is my short-ish tutorial on how to implement closures in
a simple functional language: Foo.

First, some boilerplate.

> {-# LANGUAGE DeriveFunctor, TypeFamilies #-}
> import Control.Applicative
> import Control.Monad.Gen
> import Control.Monad.Writer
> import Data.Functor.Foldable

moleike

Benchmark results

large_string_join

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
jrsonnet large_string_join.jsonnet	16.5 ± 0.5	16.1	19.6	1.00
gojsonnet large_string_join.jsonnet	90.7 ± 3.8	85.6	104.0	5.49 ± 0.29
jsonnet large_string_join.jsonnet	69.5 ± 2.4	68.2	78.1	4.20 ± 0.20
sjsonnet large_string_join.jsonnet	760.6 ± 12.7	739.9	787.2	46.00 ± 1.67

moleike

data Tm = Var Int | Ann Tm Tm | Abs Tm | App Tm Tm | Pi Tm Tm | Fix Tm | Uni
data Clos = Clos Tm Env
data Dm = DVar Int | DAbs Clos | DNeutral Int [Dm] | DPi Dm Clos | DFix Clos | DUni
type Env = [Dm]

capp :: Clos -> Dm -> Dm
capp (Clos b e) t = eval (t : e) b

vapp :: Dm -> Dm -> Dm
vapp a b =

moleike

package demo;

import java.io.Serializable;
import java.security.Principal;
import java.util.Collection;
import java.util.Collections;
import java.util.HashMap;
import java.util.Map;
import java.util.UUID;

moleike

Driver:
  -Write the code according to the navigator's specification
  -Listen intently to the navigators instructions
  -Ask questions wherever there is a lack of clarity
  -Offer alternative solutions if you disagree with the navigator
  -Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on
  -Make sure code is clean
  -Own the computer / keyboard
  -Ignore larger issues and focus on the task at hand
  -Trust the navigator - ultimately the navigator has the final say in what is written

moleike

package main

import (
	"fmt"
	"io"
	"io/ioutil"
	"net"
	"os"
	"strings"

moleike

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

moleike

obj-m += tcp_svr_sample.o
 
all:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
 
clean:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clea

moleike

Understanding the Memory Layout of Linux Executables

Required tools for playing around with memory:

• hexdump
• objdump
• readelf
• xxd
• gcore

moleike

input {
  lumberjack {
    # The port to listen on
    port => 5043

    # The paths to your ssl cert and key
    ssl_certificate => "/etc/pki/tls/certs/logstash-forwarder/logstash-forwarder.crt"
    ssl_key => "/etc/pki/tls/private/logstash-forwarder/logstash-forwarder.key"
    
    # default type, but this will already be set by logstash-forwarder anyways