evacchi

#!/bin/sh 
if [ "$1" == "" ]; then echo USAGE: pdfcompress filename; exit; fi
gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dNOPAUSE -dQUIET -dBATCH -sOutputFile=$1-compressed.pdf $1.pdf

evacchi

package org.tylproject.demos;

import com.mongodb.MongoClient;
import com.vaadin.annotations.Theme;
import com.vaadin.annotations.VaadinServletConfiguration;
import com.vaadin.server.VaadinRequest;
import com.vaadin.server.VaadinServlet;
import com.vaadin.ui.Tree;
import com.vaadin.ui.UI;
import com.vaadin.ui.VerticalLayout;

evacchi

import com.vaadin.data.Container;
import com.vaadin.data.Item;
import com.vaadin.data.Property;
import com.vaadin.data.util.filter.UnsupportedFilterException;

import java.lang.ref.SoftReference;
import java.lang.ref.WeakReference;
import java.util.Collection;
import java.util.HashMap;

evacchi

// grappa_exe.cpp
namespace PyGrappa {
	extern "C" void run();
};

int main(int argc, char **argv){
	PyGrappa::run();
}

evacchi

trait Tree
data object Empty : Tree
data class Leaf(val value: Int) : Tree
data class Node(val left: Tree, val right: Tree) : Tree

fun max(x:Int, y:Int):Int = if (x > y) x else y

fun depth(t: Tree): Int = when (t) {
    is Empty -> 0
    is Leaf  -> 1

evacchi

/**
 * You take the Blue.Pill. You wake up in your bed and believe whatever you want to.
 * Usage: <code>throw Blue.Pill</code>, then, somewhere else: 
 * try { ... } catch (Blue Pill) { /* possibly do something */ }
 * 
 * @author edoardovacchi
 */
public abstract class Blue extends RuntimeException {
    
    public static Blue.Pill Pill = new Blue.Pill();

evacchi

trait John
trait Carl
trait Tom
trait Child[T,U]
trait GrandChild[T,U]

implicit val john_carl = new Child[John,Carl]{}
implicit val carl_tom  = new Child[Carl,Tom ]{}

implicit def grandChild[X,Y,Z](

evacchi

trait John
trait Carl
trait Tom
trait Child[T,U]
trait GrandChild {
  type Left
  type Right
}
object GrandChild {
  type Left[T] = GrandChild { type Left = T }

evacchi

\documentclass{article}

\usepackage{luatex85}
\usepackage{luaotfload}
\usepackage{fontspec}

\usepackage{lecturer}
\usepackage{xcolor}

\setmainfont{Gill Sans}

evacchi

Inspired by the effort towards better documentation, I'd like to raise a few points about SBT, that I wish could be addressed. I, myself, am not against the DSL per se, but I'd like things to be more explicit. Here's a few examples:

• an empty or missing build.sbt is a valid project (unless you use sbt-extras)
• "bare" keys are not scoped per-build, but per-project, although there is no explicit project definition
• when an explicit root project is missing, sub-projects are auto-aggregated. As you introduce a root project, you'll lose auto-aggregation
• the project macro fills in the name of the project by "reading" it from the val identifier in lazy val foo = project. This is surprising because it does not behave like regular code. I'd even argue that just using Project might be clearer

other personal observations:

• scoping is still unclear (to me), because I'd expect subprojects to inherit keys from parents, while we are expected to use inThisBuild or commonSettings