From f70130322cd306268c5da12c1517dc5725615ae8 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Thu, 15 Feb 2024 12:18:17 +0000
Subject: text -> en

---
 .../lesson08_labelled_arguments/text.html          | 23 ----------------------
 1 file changed, 23 deletions(-)
 delete mode 100644 src/content/chapter1_functions/lesson08_labelled_arguments/text.html

(limited to 'src/content/chapter1_functions/lesson08_labelled_arguments/text.html')

diff --git a/src/content/chapter1_functions/lesson08_labelled_arguments/text.html b/src/content/chapter1_functions/lesson08_labelled_arguments/text.html
deleted file mode 100644
index b1d771c..0000000
--- a/src/content/chapter1_functions/lesson08_labelled_arguments/text.html
+++ /dev/null
@@ -1,23 +0,0 @@
-<p>
-  When functions take several arguments it can be difficult to remember what the
-  arguments are, and what order they are expected in.
-</p>
-<p>
-  To help with this Gleam supports labelled arguments, where function arguments
-  are given an external label in addition to their internal name. These labels
-  are written before the argument name in the function definition.
-</p>
-<p>
-  When labelled arguments are used the order of the arguments does not matter,
-  but all unlabelled arguments must come before labelled arguments.
-</p>
-<p>
-  There is no performance cost to using labelled arguments, it does not allocate
-  a dictionary or perform any other runtime work.
-</p>
-<p>
-  Labels are optional when calling a function, it is up to the programmer to
-  decide what is clearest in their code.
-</p>
-
-
-- 
cgit v1.2.3