From f6836182b6265709cdd3935d361614fde5314fae Mon Sep 17 00:00:00 2001 From: Andrea Leopardi Date: Mon, 11 Sep 2023 22:41:33 +0200 Subject: [PATCH] Update lib/elixir/pages/anti-patterns/design-anti-patterns.md --- lib/elixir/pages/anti-patterns/design-anti-patterns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/elixir/pages/anti-patterns/design-anti-patterns.md b/lib/elixir/pages/anti-patterns/design-anti-patterns.md index 6e9aeb8a024..1642e34d1c4 100644 --- a/lib/elixir/pages/anti-patterns/design-anti-patterns.md +++ b/lib/elixir/pages/anti-patterns/design-anti-patterns.md @@ -188,7 +188,7 @@ iex> Client.foo("Lucas") #### Refactoring -Library authors should guarantee that users are not required to use exceptions for control flow in their applications. As shown below, this can be done by refactoring `MyModule`, providing two versions of the function that forces clients to use exceptions for control flow: +Library authors should guarantee that users are not required to use exceptions for control flow in their applications. As shown below, this can be done by refactoring `MyModule`, providing two versions of the function that forces clients to use exceptions for control flow: 1. A version that raises exceptions should have the same name as the "janky" one, but with a trailing `!` (`janky_function!/1`);