Welcome to Swift Concurrency Course Discussions!

[AvdLee]

👋 Welcome to the Swift Concurrency Course Community!

We're thrilled to have you here! This Discussions page is a space for learners and Swift developers to ask questions, share insights, and collaborate on Swift Concurrency topics. Whether you're migrating to Swift 6 or deepening your concurrency knowledge, you're in the right place. 🚀

🔥 What can you do here?

• Ask questions – Need help understanding a lesson? Stuck on a Swift Concurrency concept? Ask away!
• Share insights – Have an interesting use case or a cool concurrency trick? Let’s discuss!
• Help others – If you see a question you can answer, jump in and share your knowledge.
• Discuss Swift 6 migration – Share your experiences and challenges with Swift 6’s concurrency updates.

📌 Guidelines

• Be respectful and supportive—we’re all here to learn.
• Keep discussions on-topic and relevant to Swift Concurrency.
• Search before posting to see if your question has already been answered.

🚀 Get Started

Introduce yourself in the comments below! Let us know:

• What brought you to this course?
• What’s your experience with Swift Concurrency so far?
• What’s one thing you’re hoping to learn?

Looking forward to great discussions! 🎉

[hujaber]

Hi @AvdLee
I finished the first section, took the quiz, scored 6/7 and now I am stuck. I can't retake it, I can't continue to the next section. Your help would be appreciated. Thanks!

[AvdLee]

Understood! I like the argument you share of "knowing where to focus", that makes sense!

I'm learning as well and like I said, I take the feedback seriously in the early stage of the course. I'll enable showing answers tomorrow as the last thing I want is creating frustration and will give it more thoughts and research in the meantime.

Do let me know if you experience anything else that can be improved!

[hujaber]

@AvdLee thanks for the update. The new mechanism is way better, I was able to figure out my mistakes and at the same time avoid getting blocked.

[AvdLee]

@hujaber amazing, glad it's directly having its impact. Once again, highly appreciate your feedback. There are probably many other students with similar experiences that don't take the time to reply and let me know. It's feedback like this that helps me build a better learning experience!

[AvdLee]

P.S. There is a misspelling "Wat" in the title of one of the questions and in another the title doesn't wrap and gets cut off at the ends (I had to guess what the question was.)

@gilroykilroy thanks for this as well, fixed both! 🙌

[gilroykilroy]

There was one more place where you had "learns" when I believe you meant "learnings". Towards the end of one of the lessons; I don't recall which.

[gilroykilroy]

OK, passed the quiz, now I am getting:

Lesson content locked
Lesson content will become available in 16 days

Do you only have the first two sections ready? Following that one it seems to have a 2 week wait between sections?

[hujaber]

Yeah the course is still being released gradually, I think the timeline is 128 days for the full course to be out

[AvdLee]

@gilroykilroy Yes, only the first two modules are available now. This is mentioned on the landing page, and it's also why you've been able to purchase the course with a discount. There's a lot of things changing in Swift Concurrency as the Swift Team concluded it's too hard to adopt Swift 6, so the timeline is needed for me to process these changes while progressively building up more content for the course.

[jzm0720]

@AvdLee Ah! I misuderstood. I sent you same question. Please disregard I understand now.
Jim

[gilroykilroy]

Does the "Add Async Alternative" Xcode command work? Seems if I try it on a non-trivial example (say the performPOSTURLRequest in the module 2 sample code) it comes up with an alert that says "Refactoring failed. Connection interrupted" and/or "Refactoring failed. semantic editor is disabled"

If I try it on a trivial example, taking performPOSTURLRequest and simply calling completion(.failure(.invalidResponse)) it works fine. Something to report to Apple or something I may have wrong at my end?

[AvdLee]

Same here:

Looks like a bug to me that's worth reporting.