summaryrefslogtreecommitdiff
path: root/sec/reducer.ltx
blob: c73a4f616eb7bd662ac4427bc145330256aef731 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
\documentclass[../main.tex]{subfiles}

\begin{document}
\section{Writing ARTyST Programs}%
\label{sec:reducer}

We have used \lang{} to write two non-trivial programs that can be
embedded in System~T. The first is a fuelled reducer for
System~T. Given \(n\) units of fuel, the reducer will perform \(n\)
steps of complete~development~\cite{cd} on a System~T term. The second
program is the encoding from \lang{} to System~T. This takes a
type-annotated \lang{} program and encodes it as a System~T term.

\TODO{
  \begin{itemize}
    \item describe the syntactic sugar I have added
  \end{itemize}
}

\TODO{
  \begin{itemize}
    \item describe the operation of the fuelled reducer
    \item explain why fuel is necessary for the reducer
    \item show some example snippets
  \end{itemize}
}

\TODO{
  \begin{itemize}
    \item describe the inputs to the embedding
    \item describe the output of the embedding
    \item show a ``non-destructive'' fold
    \item justify use of destructive folds
  \end{itemize}
}

\TODO{
  \begin{itemize}
    \item describe why encoded terms have lots of beta redices
    \item describe potential benefit of composing two programs
    \item explain the limitiations of the reducer (e.g. eta and bools)
  \end{itemize}
}

\end{document}