https://docs.swift.org/swift-book/documentation/the-swift-programming-language/concurrency
On the official documentation page about Swift Concurrency, some codes are mis matched context, difficult to understand I found. And I'm really new to programming, so I wonder, if there are any other lessons about Concurrency can reached? Thx~
The Swift 6 migration guide might be helpful too, though it isn't quite the same thing Documentation
The place I tell folks to start is WWDC 2022 Session 110351 Eliminate data races using Swift Concurrency. It introduces the ‘sailing on the sea of concurrency’ model, which is a key first step.
Beyond that:
I’ll second @mattie’s recommendation of Migrating to Swift 6.
And also recommend his blog, which I read avidly.
I also like WWDC 2021 Session 10134 Explore structured concurrency in Swift, and most specifically the table that starts rolling out at around 25:45.
Share and Enjoy
Quinn “The Eskimo!” @ DTS @ Apple
I found "Practical Swift Concurrency" by Donny Wals insightful and helpful as a beginner.
Some totally sideways advice here would be to maybe explore any resources from the JS community for teaching async-await (which shipped on JS long before Swift).
The Apple and Swift Ecosystem (IMO) do a good job at teaching Swift-Specific ideas and patterns to engineers who already have a lot of professional or academic experience with engineering. Historically (IMO) the documentation from Apple (going back to the ObjC days) is not the best place for someone to literally learn engineering from scratch. This was usually a space for companies like Big Nerd Ranch to step in and fill in those gaps.
It's possible that there might be some JS resources for "thinking" in async-await that maybe click with you more than what Apple and Swift are currently publishing (and then the Apple documentation all starts to make a lot more sense).
I'm not asking you to become a JS specialist… but just offering a different POV. In general I would also say this is a good skill to develop as an engineer… learn how other ecosystems and languages approach similar problems and then use that to help you become a better engineer in your chosen specialization (like Swift). But YMMV and I realize a lot of engineers have different learning styles. Good luck!