There is also the Editor menu > Preview

Yes, post your mail here please.

Working with someone since a year is not enough (in my mind) to create absolute trust… Can you meet them in person, not remotely ?

If you wanted to remove from self.trades, you should: find what is the position in trades of the section/row you remove (it is NOT indexPath.row). Then remove it from self.trades. After that, recompute self.sections dictionary with self.sections = groupBySymbol.map {(Key, Value) in return sectionBySymbol(symbol: Key, trades: Value) }. So it is much simpler to update sections[indexPath.section].trades directly.

So you had seen the answer on SO, and seen the answer there was essentially same as mine: no generic solution to solving. Note: if you set one of the unknown, you will not explore the whole surface and will probably fall out of the intersection. But if that fits your needs, that's OK? Good luck.

Once solved, what should the intersect func return ?

If you don't see any difference between Swift 2 and Swift 5, you may have overlooked this ? https://github.com/apple/swift/blob/main/CHANGELOG.md

It's better, but would be even better with explicit info. Which is First report in your sum up ? Which are its actions ? What is Block alert ? etc…

Thanks for feedback. You can test with @State var text = "vak", to see Text change when tapping button. Don't forget to close the thread.

Thanks, interesting information. But it would be so much better to have code snippets in the documentation.

But doc describes how it is supposed to work. For instance: "In the following example of a simple login screen, when the user presses the Sign In button and one of the fields is still empty, focus moves to that field. Otherwise, the sign-in process proceeds."

That what it says if you read just the first line. A field being edited is focused, a field may be focused without being edited. If you go through and make the effort to understand the examples, you will understand what they are. Sure, it is some effort, as for every learning… Good luck.

This may be an interesting read: https://stackoverflow.com/questions/68731011/when-is-deinit-exactly-called-in-swift

Thanks for the feedback, and great to read your app works now. As you get the log (RAMBar nil), that means the crash is just after, on the second print.

Thanks for the feedback. Note: you don't even need .searchable(text: $searchText). When TextField changes, State var searchText is changed, then body is reevaluated.