Throwing factories and resolve dependencies block

[ilyapuchka]

With that PR we no more need to call container.resolve() with try! inside a factory or resolveDependencies block. Also convenient to use throwing constructors or any other throwing methods inside those blocks. Error will be catched by container, printed in console and then will be re-thrown.

Note: There is no way (at least for now) I can think of to be able to distinguish between throwing and not-throwing factories (thus the latest definition will override previous), except of duplicating all register/resolve methods, what I don't like at all cause it will double the number of methods in container. Taking in account that tag is an optional argument and we have support for 6 runtime arguments already (and upcoming multi-injection feature will ad 6 more methods) it will make API too much bloated.

[AliSoftware]

Not sure if the outer throws should be throws or rethrows?

http://robnapier.net/re-throws

[ilyapuchka]

Here rethrows will not compile cause this method throws error itself.

[AliSoftware]

Just make sure you double-check every time you use (f: … throws) -> throws if it's valid or if a rethrows might instead be used. But apart from that LGTM.

[AliSoftware]

Note: once you merge that, make sure to rebase #13 before merging it, as I'm wondering if this change might have impacts on the playground / example code you added there too, like changing calls using try there?

[ilyapuchka]

Looks like _resolve is the only place where rethrows is applicable, except ResolvedInstances.resolve where it is already used.

[AliSoftware]

👌

[ilyapuchka]

Good catch, these changes actually broke #13 😞 will try to figure out the fix

[ilyapuchka]

Fixed the issue, it is safe to merge this now 🎉