Understanding Swift Initializers

[@stephaniewagstaff6563]

I’m only through first 5 minutes and your explanation exploded the brick wall in front of me getting this! Your are truly the best instructor out there!

[@gakkieNL]

Love the final swiftUI part!

[@robertdavis7262]

Great job again! I didn't expect to learn anything from this one, but I was wrong. Thanks

[@StewartLynch]

Glad you liked it!

[@parietal100]

Thanks Stewart. Another great review.

[@StewartLynch]

Thanks. I am glad you think so.

[@mhfs61]

It finally clicked with me. Thank you Stewart.

[@nigelgee3576]

Just a quick note that if you create an extension on a struct and add the other init() then you do not lose the member wise init

[@StewartLynch]

Right. Thanks for pointing that out Nigel

[@andrejkling3886]

Special thanks for SwiftUI example ... 👏 if you can create video about how better understand documentation ... it´s will be amazing!

[@andresraigoza2082]

Thank you so much Stewart

[@StewartLynch]

You are very welcome

[@DavidKoontz]

Great content. The explanation of adding the init doc comment to make the quick help display the help text for API explanation should be required watching for API Producers!

[@jonothen2212]

Great work Stewart learned a ton

[@tikl21]

Awesome! thanks so much

[@paul7000]

this vid is brilliant

[@StewartLynch]

Thanks

[@trungnguyenthanh9233]

Nice content

[@dibjr]

In Xcode 14.3 I get a bunch of 'unknown context at $....' in the statement results frame for the let statements, which I don't see in your video. They appear to not have a bad effect.

[@dibjr]

Here is an example in ConvenienceInitializers. The statement: let p1 = Person(name: "Henry", age: 24) shows the following in the statement results: (unknown context at $102b38a2c).(unknown context at $102b38a80).(unknown context at $102b38a88).Person

[@victorriurean]

nice

[@yt-1161]

audio sounds tinny in this part

[@StewartLynch]

What abut the content? I have changed my audio gear since then.

[@yt-1161]

@@StewartLynch content is great, unique, but hard to follow with my 2011 iMac. Xcode is so slow, need to get a newer machine

[@StewartLynch]

Yup, a 13 year old Mac is quite dated