From d42c20117ce91558d7bb5e6dc516df4043e88078 Mon Sep 17 00:00:00 2001 From: Sasha Koshka Date: Wed, 12 Oct 2022 07:21:16 +0000 Subject: [PATCH] Update 'Error Handling' --- Error-Handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Error-Handling.md b/Error-Handling.md index f897830..36977b9 100644 --- a/Error-Handling.md +++ b/Error-Handling.md @@ -10,7 +10,7 @@ When writing error messages, present the user with something very plain. Do not For example, say you wanted to produce an error when a value of one type can't be passed as another type. You could do: ``` -type mismatch: cannot pass String:1 (aka {U32 ..}:1) into U64:1 +type mismatch: cannot pass U64:1 into String:1 (aka {U32 ..}:1) ``` ... Which is messy, and contains useless information, thereby sacrificing clarity. You could try: