Skip to content

Commit

Permalink
Replace the make_thunk section with a section that introduces Op params.
Browse files Browse the repository at this point in the history
  • Loading branch information
abergeron committed Jan 31, 2017
1 parent c69fe85 commit 4e3eee3
Showing 1 changed file with 27 additions and 7 deletions.
34 changes: 27 additions & 7 deletions advanced.tex
Original file line number Diff line number Diff line change
Expand Up @@ -351,23 +351,43 @@ \section{How to Make an Op (C)}
\end{itemize}
\end{frame}

\section{How to Make a Complex Op}
\section{Op Params}

\begin{frame}[plain]{}
\begin{center}
\Huge How to Make a Complex Op
\Huge Op Params
\end{center}
\end{frame}

\begin{frame}{\code{make_thunk}}
\lstinputlisting[linerange={12-14}]{thunk.py}
\begin{frame}{Purpose}
\begin{itemize}
\item Define instead of \code{perform} or \code{c_code}
\item Gives total freedom on how the computation is performed
\item More complex to use and generally not needed
\item Used to pass information to the C code
\item Can reduce the amount of compiled C code
\item Required for things that can change from one script run to the other.
\end{itemize}
\end{frame}

\begin{frame}{Usage}
\lstinputlisting{params.py}
\end{frame}

%\section{How to Make a Complex Op}

%\begin{frame}[plain]{}
%\begin{center}
%\Huge How to Make a Complex Op
%\end{center}
%\end{frame}

%\begin{frame}{\code{make_thunk}}
%\lstinputlisting[linerange={12-14}]{thunk.py}
%\begin{itemize}
%\item Define instead of \code{perform} or \code{c_code}
%\item Gives total freedom on how the computation is performed
%\item More complex to use and generally not needed
%\end{itemize}
%\end{frame}

\section{Optimizations}

\begin{frame}[plain]{}
Expand Down

0 comments on commit 4e3eee3

Please sign in to comment.