The description and method declaration of Any.equals should use the same parameter name in ScalaDoc

[scabug]

The description in the ScalaDoc of Any.eqauls() states:

"Compares the receiver object (this) with the argument object (that) for equivalence."

but the argument name is "arg0". The description and method declaration should be the same.

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-6684?orig=1
Reporter: graham seed (gmseed)
Affected Versions: 2.9.2, 2.10.0-M3

[scabug]

@soc said:
This is weird, because the parameter names are actually correct when looking at the source file. Maybe there is some library-aux magic happening of which I'm not aware of ...

[SethTisue]

same in 2.12.4

[mado-m]

same in 2.13.0
It is strange.

[nogurenn]

I tried searching the scaladoc website for "equals", and it's dominated by the arg0 parameter. Not a good sight, to be honest.

I thought about the parameter arg0, and I figured to do a quick search online because I think it's being generated by something really implicit. See this (https://stackoverflow.com/questions/18556400/some-function-parameters-named-arg0-arg1-etc-after-compiling-a-jar-library).

I guess the questions I have are: (1) is scaladoc generating the docs based on the compiled classes/files, and (2) is the bootstrapping/compilation process for library-aux explicitly accounting for the automatically generated argN params. I'm also asking about (2) because build.sbt only references library-aux in the variable library, and because the README inside explicitly says files residing there cannot be compiled by normal means.

[Jasper-M]

Note that at compile time the parameter of equals is called x$1, which is also some default name for parameters whose names are not present in the class file.

What I find the weirdest is that the Scaladoc uses arg0 instead of x$1, which suggests that it doesn't just take the names from the method symbol in the compiler, but it doesn't use the names from the source code either.