Currently, when javac encounters a javadoc reference, like `@see
PrintStream#println(int)`, will first try to find a method `println` in
`PrintStream` using subtyping on the argument types, which may find another
overload of the method with an argument that is a subtype of `int` - like
`println
On Tue, 4 Jan 2022 17:19:44 GMT, Jan Lahoda wrote:
> Currently, when javac encounters a javadoc reference, like `@see
> PrintStream#println(int)`, will first try to find a method `println` in
> `PrintStream` using subtyping on the argument types, which may find another
> overload of the method
On Tue, 4 Jan 2022 17:19:44 GMT, Jan Lahoda wrote:
> Currently, when javac encounters a javadoc reference, like `@see
> PrintStream#println(int)`, will first try to find a method `println` in
> `PrintStream` using subtyping on the argument types, which may find another
> overload of the method
On Tue, 4 Jan 2022 17:19:44 GMT, Jan Lahoda wrote:
> Currently, when javac encounters a javadoc reference, like `@see
> PrintStream#println(int)`, will first try to find a method `println` in
> `PrintStream` using subtyping on the argument types, which may find another
> overload of the method
