Comment #14 on issue 757 by sberlin: Java 8 lambda definitions can break
Guice's internal exception handling
http://code.google.com/p/google-guice/issues/detail?id=757
I respectfully disagree. Arbitrarily adding try/catch around places just
leads to brittle code that can magically succeed or fail without knowing
what's going on. Guice (and the libraries it embeds right now) do not
expect things to fail in this kind of way, and it is good to blow up when
it encounters something that will cause it to fail. Stuart's suggested
changes from earlier are the best approach IMO (either exposing the problem
more transparently, or solving it entirely).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice-dev.
For more options, visit https://groups.google.com/groups/opt_out.
