Open reid-spencer opened 1 year ago
@Dedelweiss Could you have a look at this issue?
So from what I've noticed in my tests. I don't think the problem comes directly from Dotty but from the Scalatest comments used by Scaladoc. In fact, I've isolated the problem in a smaller project with the scalatest dependency and the Assertion
and AnyWordSpec
imports and I end up with the same warnings.
I think it's the @throws
that are incorrectly handled or something like that. I'll take a deeper look and see what I can do.
In Scalatest.Assertions.scala:
Hello @reid-spencer, thank you for waiting. The problem does indeed come from Scalatest (and perhaps Dotty too). I'll see later if it's an Issue but currently Scaladoc can't make the link to the classes in the throws
parameter of the comments if there isn't a complete path.
So I've made a PR on Scalatest to correct it, erase the warning and now I just have to wait for it to pass.
I'll keep you informed of any progress. Thank you very much.
It seems in Scala 2 it was possible to use a symbol in a Scaladoc directive without writing its fully qualified name if the symbol was previously imported. It would be good to support the same in Scala 3. Do you know what it would take?
@ Dedelweiss & julienrf Thanks for the analysis. I have noted in Scala2, many times, that a fully qualified name is needed in references to code. Your help is appreciated but I don't think this is a major issue, unlike #17577 which is a blocker for me.
Compiler version
3.3.0-RC6
Minimized code
The symptom occurs in https://github.com/reactific/riddl/testkit only. Other modules in that repository do not produce the symptomatic warnings. The warnings relate to code locations within the compiler, not within in the input source.
Output
Expectation
The warnings are not put out.