{"id":17949,"date":"2022-10-28T02:38:38","date_gmt":"2022-10-27T21:08:38","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-i-do-not-understand-what-this-code-doesthe-code-is-about-segues\/"},"modified":"2022-10-28T02:38:38","modified_gmt":"2022-10-27T21:08:38","slug":"solved-i-do-not-understand-what-this-code-doesthe-code-is-about-segues","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-i-do-not-understand-what-this-code-doesthe-code-is-about-segues\/","title":{"rendered":"[Solved] I do not understand what this code does(the code is about segues)"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

That’s not the best segue code. Here’s how I’d code it (for the record, there are several ways to code this):<\/p>\n

override func prepare(for segue: UIStoryboardSegue, sender: Any?) {\n    if segue.identifier == \"[segue name here]\" {\n        if let nextVC = segue.destination as? CreateTasksViewController {\n            nextVC.tasksVC = self\n        }\n    }\n}\n<\/code><\/pre>\n
The code you posted has what is called a “forced unwrap”<\/a> of the segue destination (that’s the as!<\/strong> you asked about). Here’s a question with a pretty good answer explaining the dangers of forced unwrapping. Scroll down to the divider in the answer.<\/p>\n
While I’m sure the code compiles (and likely runs), the problem is code maintenance.<\/p>\n
Suppose you have several segues defined between several scenes, each with their own view controller? My code, as matter of style, gives up a bit of “Swiftiness” for “explicitness”:<\/p>\n