The \glspl{Task} suitable for a client are called \gls{mTask}-\gls{Task} and
are written in the aforementioned \gls{mTask}-\gls{EDSL}. Some functionality of
the original \gls{mTask}-\gls{EDSL} will not be used in this system.
Conversely, some functionality needed was not available in the existing
\gls{EDSL}. Due to the nature of class based shallow embedding this obstacle is
easy to solve. A type --- housing the \gls{EDSL} --- does not have to implement
all the available classes. Moreover, classes can be added at will without
interfering with the existing views.

\section{\gls{Task} Semantics}
\input{mtaskext.tasksem}

\section{\gls{SDS} semantics}
\input{mtaskext.sdssem}

\section{Bytecode compilation view}\label{sec:compiler}
\input{mtaskext.bytecode}

\section{Examples}
\input{mtaskext.examples}
