From 1b0804e10cae4cb4b0ce6399e0f09179572ca73e Mon Sep 17 00:00:00 2001 From: Brent Simmons Date: Thu, 6 Sep 2018 19:22:38 -0700 Subject: [PATCH] Update Coding Guidelines to mention Swift 4.2 and to specify tabs over spaces. --- Technotes/CodingGuidelines.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Technotes/CodingGuidelines.md b/Technotes/CodingGuidelines.md index 9c3665f6b..957eba404 100644 --- a/Technotes/CodingGuidelines.md +++ b/Technotes/CodingGuidelines.md @@ -26,7 +26,7 @@ Similarly: always work at the highest level possible, but not higher and certain ### Language -Write new code in Swift 4. +Write new code in Swift 4.2. The one exception to this is when dealing with C APIs, which are often much easier to deal with in Objective-C than in Swift. Still, though, this is rare, and is much more likely to be needed in a lower-level framework such as RSParser — it shouldn’t happen at the app level. @@ -167,3 +167,7 @@ Every commit message should begin with a present-tense verb. Don’t show off. If your code looks like kindergarten code, then _good_. Points are granted for not trying to amass points. + +### Really Last Thing + +Tabs vs. spaces? Tabs. We had to pick, and we picked tabs, because it lets people decide their own tab width.