We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@CalledMethods annotations currently bucket overloaded methods. So, for example, if we had this class:
@CalledMethods
class OverloadingExample { void a(); void a(Object foo); }
then these two sequences of method calls would result in an object with the same type (@CalledMethods({"a"})):
@CalledMethods({"a"})
OverloadingExample o1 = new OverloadingExample().a(); OverloadingExample o2 = new OverloadingExample().a(null);
We haven't seen an instance where this distinction is important yet, but it is a limitation of the current type system.
The text was updated successfully, but these errors were encountered:
required.method.not.called
No branches or pull requests
@CalledMethods
annotations currently bucket overloaded methods. So, for example, if we had this class:then these two sequences of method calls would result in an object with the same type (
@CalledMethods({"a"})
):We haven't seen an instance where this distinction is important yet, but it is a limitation of the current type system.
The text was updated successfully, but these errors were encountered: