You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accessing the reference through the API docs shows a This is a nightly documentation. The content of this page may not be consistent with the current stable version of language warning message, even when a stable version of the language is chosen: https://scala-lang.org/api/3.3_LTS/docs/docs/reference/syntax.html
Expectation
No warning message on stable versions.
I remember on older versions of the compiler, the scaladoc API would not be able to show the scala 3 reference (https://scala-lang.org/api/3.3.1/) on the stable versions of the compiler, instead having it completely separate (https://docs.scala-lang.org/scala3/reference/new-types/intersection-types.html). I suspect this merger is when the issue appeared, as previously we were only able to access reference through the API docs only on nightly versions of the scaladoc (though I personally like that they are now always merged)
The text was updated successfully, but these errors were encountered:
Accessing the reference through the API docs shows a
This is a nightly documentation. The content of this page may not be consistent with the current stable version of language
warning message, even when a stable version of the language is chosen:https://scala-lang.org/api/3.3_LTS/docs/docs/reference/syntax.html
Expectation
No warning message on stable versions.
I remember on older versions of the compiler, the scaladoc API would not be able to show the scala 3 reference (https://scala-lang.org/api/3.3.1/) on the stable versions of the compiler, instead having it completely separate (https://docs.scala-lang.org/scala3/reference/new-types/intersection-types.html). I suspect this merger is when the issue appeared, as previously we were only able to access reference through the API docs only on nightly versions of the scaladoc (though I personally like that they are now always merged)
The text was updated successfully, but these errors were encountered: