Context Functions code snippet seems to have wrong indentation

[peter-jerry-ye]

Hi,

On my computer, the code snippet of Context Functions seems to have wrong indention. Tested it both on Edge 106.0.1370.52 and Firefox 106.0.1, I'm using Windows 10 21H2.

Here's how it looks like:


And here's how the pasted code (by using the paste button) executes:

[SethTisue]

I would transfer the issue to https://github.com/scala/docs.scala-lang if GitHub allowed transferring issues between orgs. (It's unfortunate that this repo is still called lampepfl/dotty rather than scala/scala3 — there was talk of changing it, haven't heard an update recently about that.)

I agree that the code block needs to be fixed, and so does the one after it. A PR over in the other repo would be welcome.

[peter-jerry-ye]

I would transfer the issue to https://github.com/scala/docs.scala-lang if GitHub allowed transferring issues between orgs.

Thank you for your help. Actually I posted it here because the Edit this page on GitHub link on the page actually points to a branch in this repo. Maybe that should also be changed?

[peter-jerry-ye]

I checked that repo, and it says:

The content of the pages https://docs.scala-lang.org/scala3/reference is generated from the Scala 3 compiler repository.

Please go here to contribute to the Scala 3 reference documentation:

https://github.com/lampepfl/dotty/tree/main/docs/_docs

But in the main branch the indention is correct, and according to git blame the last modification was 3 years ago. That is quite weird.

[SethTisue]

The content of the pages https://docs.scala-lang.org/scala3/reference is generated from the Scala 3 compiler repository

Oh boy.

There has a bunch of activity in this area recently that I haven't followed closely. @Sporarum can you clarify?

[Sporarum]

The changes will indeed have to be done on this repo
Aside: It is done this way to try to force developers to update documentation alongside their changes to the compiler, to ensure the former is up-to-date at all times
(And the current goal would be for the spec to be here as well, for the same reasons)

On the question of whether the issues should be open here or over there, I believe (weakly) here is more convenient

As for moving this repo to scala/scala3, I agree with it in theory, but do not know the details/limitations/... of that change
I believe this discussion could be interesting on the contributors forum

If there are still some areas that are unclear, feel free to ask