I appreciate the detailed response. I really do. The bottom line for me is that my productivity grinds to a halt if any debugging is involved. For my client work this would be an absolute show stopper for using Swift.
I frequently see the problem shown by @cukr upthread. I'll see about filing a bug on it.
Another issue I see a lot is objects where all the ivars are nil or "". When I po those objects then I see the ivar values. Maybe I can come up with a reproducible case. Took me a long time to realize this was a debugger bug.