You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the codacy PMD issues, I recognize that we currently seem to avoid having checked exceptions when using reflections by catching them and throwing unchecked raw RuntimeException. An example can be found in org.opt4j.core.Genotype newInstance() and then considering the implementation of the interface in org.opt4j.core.genotype.IntegerGenotype.
What's your opinion on how to address this? Obviously, we want to back out anyway in case the newInstance() function throws any of the checked exceptions and just choosing an unchecked Exception that is not raw RuntimeException may also be considered artificial PMD appeasement. :-)
The text was updated successfully, but these errors were encountered:
While working on the codacy PMD issues, I recognize that we currently seem to avoid having checked exceptions when using reflections by catching them and throwing unchecked raw RuntimeException. An example can be found in org.opt4j.core.Genotype newInstance() and then considering the implementation of the interface in org.opt4j.core.genotype.IntegerGenotype.
What's your opinion on how to address this? Obviously, we want to back out anyway in case the newInstance() function throws any of the checked exceptions and just choosing an unchecked Exception that is not raw RuntimeException may also be considered artificial PMD appeasement. :-)
The text was updated successfully, but these errors were encountered: