100 days of swiftUI

在職中不在iOs生態但寫的swift太少 也不想純刷題也想寫點project邊上手swiftUI 恰好100days of swiftUI是需要每天打卡分享所學的！所以在此紀錄
day1: topic: simple vars/let string interpolation/type inference. 就基本中的基本 建議下unwrap app可以順便test

Day 2: collections
Swift provides probably one of the most powerful enum collection type. I found it very useful and practical.

Day3 operators and conditions: swift term - 1 to 5: 1...5; 1 through 5: 1..<5
Covering range to NSrange(use case: working with NSAttributedString)
NSString and NSRange(String is a collection of characters; not every character is the same size), thus use Range<String.Index> instead of Range<Int> to get the actual size of a character.

Day 3: loops
Outer loop label can be used for Continue but never see it in production code so far.

Day 4: functions
Inout, variations functions
Reading:
try?try! Rethrow Not quite covered in the topic, but try? Always return optional, so be aware when the function returns an optional, might confuse if the optional is a rerun value or a thrown error.

Day 5 closure- part1:
Basic closure syntax

Day7(repeating day3 at loop)
Closure-part2:
What I learnt: more syntax of closure, simple example of implementation of reduce(), capturing values of closure
Additional reading: closure capture reference of any type, the reference lives with closure life cycle- that mean we can modify reference a variable use in a closure; less comply seen: capture list [var = var2] in closure
Advanced topic: weak self/unowned self for closure/@escape

Day 8: structure 1
Computed property, did set/willSet, string/array are also implemented using struct

julyVAHF 发表于 2021-09-03 23:14:09
Day 8: structure 1
Computed property, did set/willSet, string/array are also implemented using struc

Property Observer: did set/willset

Day 9: struct part 2:
What I learnt: Lazy initialization, access control
Reading: no need to write self when referencing other instance or methods with the closure
Closure is not escaping so no need to do weak self
If a property can be accessed by multiple threads there’s no guarantee that it will be initialized only once if several threads access the property at the same time before the initial value is set