From b4ca94c9d46ca90b83d089a00550caaad9d8b80b Mon Sep 17 00:00:00 2001 From: Ashton Williams Date: Wed, 12 Feb 2020 16:07:29 +1100 Subject: [PATCH] =?UTF-8?q?Update=20=E2=80=9CNever=E2=80=9D=20article=20re?= =?UTF-8?q?ference=20to=20Result=20type?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit At the time of the article Swift didn’t have a standard Result type, I changed the wording to reflect that it now does but didn’t at the time of the evolution proposal the paragraph is talking about. Done on mobile so might have missed something or this could be worded better? Use another PR or suggest changes for me to make - no problem either way. --- 2018-07-30-never.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2018-07-30-never.md b/2018-07-30-never.md index bbe5edc4..4bd40eb2 100644 --- a/2018-07-30-never.md +++ b/2018-07-30-never.md @@ -123,7 +123,7 @@ conforming this obscure type to `Equatable` and other protocols this way: > to represent something that always errors > or use `Never` for its `Error` to represent something that never errors. -Swift doesn't have a standard `Result` type, +Swift didn't have a standard `Result` type at the time, but most of them look something like this: ```swift