From 35efa58f5fecd33b1af69e43f8998f41774a4c74 Mon Sep 17 00:00:00 2001 From: Timothy John Perisho Eccleston Date: Fri, 14 Dec 2018 02:19:04 -0600 Subject: [PATCH] typo: "are" -> "or" --- notebooks/WhyScala.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/notebooks/WhyScala.md b/notebooks/WhyScala.md index 19f4b1a..9544ca5 100644 --- a/notebooks/WhyScala.md +++ b/notebooks/WhyScala.md @@ -29,7 +29,7 @@ Scala is a _multi-paradigm_ language. Code can look a lot like traditional Java 1. **Immutable values:** Mutability is a common source of bugs. 1. **Functions with no _side effects_:** All the information they need is passed in and all the "work" is returned. No external state is modified. 1. **Referential transparency:** You can replace a function call with a cached value that was returned from a previous invocation with the same arguments. (This is a benefit enabled by functions without side effects.) -1. **Higher-order functions:** Functions that take other functions as arguments are return functions as results. +1. **Higher-order functions:** Functions that take other functions as arguments or return functions as results. 1. **Structure separated from operations:** A core set of collections meets most needs. An operation applicable to one data structure is applicable to all. However, objects are still useful as an _encapsulation_ mechanism. This is valuable for projects with large teams and code bases.