From 0dbbe726f3a9449a2595e0feb5b8a3a061a1ecad Mon Sep 17 00:00:00 2001 From: nek0 Date: Thu, 9 Jan 2020 02:44:20 +0100 Subject: [PATCH] renaming and clarifying concepts --- Functional programming.tex | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Functional programming.tex b/Functional programming.tex index a8edaf5..114ef34 100644 --- a/Functional programming.tex +++ b/Functional programming.tex @@ -103,19 +103,19 @@ \begin{frame} \frametitle{Core Concepts} \begin{itemize} - \item \underline{Pure functions}\\ - {\onslide<2->{\color{lightgray}A (pure) function must produce the same + \item \underline{Purity}\\ + {\onslide<2->{\color{lightgray}A pure function must produce the same result given the same input and does not rely on or alter external state.}} - \item \underline{Non-imperative functions}\\ + \item \underline{Non-imperativeness}\\ {\onslide<3->{\color{lightgray}A function is not a sequence of commands, but a nesting of other functions.}} - \item \underline{First class citizens}\\ + \item \underline{First Class Citizenship}\\ {\onslide<4->{\color{lightgray}Functions are equal to other data objects and can thus be passed as function arguments or be computation results themselves.}} \item \underline{Closures}\\ {\onslide<5->{\color{lightgray}Functions can only access variables inside - context they have been created. This can happen even when the function + context they have been created. This is possible even when the function itself has left this context. In this case the variable values are frozen at the moment of departure inside the function.}} \item \underline{Lambdas}\\