[FMFP] Notes on tasks, checklist

This commit is contained in:
2026-07-28 09:19:56 +02:00
parent 3fe6b41d8b
commit 516a85a8b5
3 changed files with 16 additions and 1 deletions
@@ -17,6 +17,9 @@ For the cases notation, there are equal signs. We can use underscores as a ``don
Always consider making use of functions defined in previous subtasks. This can save a lot of time.
Note that in a type definition using \texttt{data}, everything beyond the equality sign is part of an argument of the type.
So e.g. in a type like \texttt{data LTS = LTS Transition Int}, \texttt{LTS} also needs to be supplied.
\subparagraph{Lists}
In list comprehensions, to draw from a list, \texttt{<-} is used, to delimit the description of the list contents from the generator part, we use a pipe character
and to separate each statement in the generator part, we use a comma.
@@ -1,7 +1,19 @@
\subsection{Checklist}
\subsubsection{Learning}
These are (some of) the things that we need to learn by heart for the exam
\begin{todolist}
\item Haskell prelude functions (see summary of prelude on ComSol)
\item Definition of fold functions
\item Definition of canonical function
\item LTL symbols
\item Induction scheme (especially structural induction and shape of derivation tree)
\item Ideally for shortness the CYP syntax (roughly, they said they'd not deduct points for incorrect CYP syntax)
\item Promela syntax
\end{todolist}
\subsubsection{For the exam}
\subsubsection{What to bring to the exam}
\begin{itemize}[label=$\square$]
\item Multiple colours of highlighters (for eval tasks)
\item Enough pencils
\item Probably won't be needed / allowed, but some spare paper (for notes)
\end{itemize}