|
|
@ -414,7 +414,7 @@ implementation of a programming language with various distinct |
|
|
second-class control idioms such as async/await, coroutines, etc, |
|
|
second-class control idioms such as async/await, coroutines, etc, |
|
|
because compiler engineers need only implement and maintain a single |
|
|
because compiler engineers need only implement and maintain a single |
|
|
control mechanism rather than having to implement and maintain |
|
|
control mechanism rather than having to implement and maintain |
|
|
individual runtime support for each control idiom in the source |
|
|
|
|
|
|
|
|
individual runtime support for each control idiom of the source |
|
|
language. |
|
|
language. |
|
|
|
|
|
|
|
|
% \subsection{Flavours of control} |
|
|
% \subsection{Flavours of control} |
|
|
@ -427,9 +427,10 @@ language. |
|
|
\section{State of effectful programming} |
|
|
\section{State of effectful programming} |
|
|
|
|
|
|
|
|
The evolution of effectful programming has gone through several |
|
|
The evolution of effectful programming has gone through several |
|
|
characteristic phases. In this section I will provide a brief overview |
|
|
|
|
|
of how effectful programming has evolved as well as providing a brief |
|
|
|
|
|
introduction to the core concepts concerned with each phase. |
|
|
|
|
|
|
|
|
characteristic time periods. In this section I will provide a brief |
|
|
|
|
|
programming perspective on how effectful programming has evolved as |
|
|
|
|
|
well as providing an informal introduction to the core concepts |
|
|
|
|
|
concerned with each time period. |
|
|
|
|
|
|
|
|
\subsection{Early days of direct-style} |
|
|
\subsection{Early days of direct-style} |
|
|
|
|
|
|
|
|
|