Right, that’s the Java issue. It becomes very easy to just add “throws Exception“ all over the place to silence warnings when things start to get tricky. Becau

Right, that’s the Java issue. It becomes very easy to just add “throws Exception“ all over the place to silence warnings when things start to get tricky. Because Swift forces the keyword ‘try’ (or a variant) before calling code that may throw it ends up being a lot of work to try to avoid the issue just by making everything throw. It’s much easier to do the correct thing and just handle the error in a smart place.