In case of separately compiled class files, a method reference that should be in a class is actually found in an interface.
I didn't check if this would still be executable bytecode, but I think it is better for OPAL to continue trying to provide reasonable analysis results while warning users about the problem rather than throwing an assertion error in development mode and silently doing nothing in production mode.
In case of separately compiled class files, a method reference that should be in a class is actually found in an interface.
I didn't check if this would still be executable bytecode, but I think it is better for OPAL to continue trying to provide reasonable analysis results while warning users about the problem rather than throwing an assertion error in development mode and silently doing nothing in production mode.