ThrawnCA
ThrawnCA
@lars-sh Your unit test is looking for the wrong string.
> @ThrawnCA, I didn't expect that. Might you help me: Which string should be replaced by what else? edu.umd.cs.findbugs.ba.Issue1338Test > testMethodCallInTryWithResource FAILED java.lang.AssertionError: Expected: Iterable containing exactly BugInstance with: bugType="RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE",...
Looks okay from a general code quality perspective, though I'm not an expert on the bug detection logic. Please try to avoid force-pushing, as it messes up the history (eg...
Please *don't* force-push.
> Sorry, it was because I rebased it to the current master. What is the official policy for that? The golden rule of rebasing is, "If you have published your...
Theoretically it is possible to run SpotBugs on any Java bytecode. In practice, Kotlin probably generates patterns that SpotBugs doesn't like, but you could probably just write exclusion rules for...
Depends on exactly what byte code it generated. Maybe Kotlin avoids whatever the bug was?
Are malicious subclasses really a serious concern? There are reasons that the Security Manager is going away...
SpotBugs doesn't always handle lambda functions well.
OK, technically it's not *uncallable*, but if you're defining an anonymous `Runnable`, why not name it consistently? return new Runnable() { void run() {} }::run; Or do things the regular...