update docs for 3.2.0

Author: bishabosha

docs/_blog/_posts/2017-05-31-first-dotty-milestone-release.md

@@ -72,7 +72,7 @@ This technology preview demonstrates new language features planned for Scala 3:
 
 We also ship with tools that help you try out the Dotty platform:
 
-  - [IDE features for Visual Studio Code](https://dotty.epfl.ch/docs/usage/ide-support.html)
+  - [IDE features for Visual Studio Code](https://docs.scala-lang.org/scala3/getting-started.html#using-vscode-with-metals)
   - [sbt support, including retro-compatibility with Scala 2](https://github.com/lampepfl/dotty-example-project)
 
 See here for the full [release notes](https://dotty.epfl.ch/docs/release-notes/0.1.2.html).

docs/_blog/_posts/2017-07-12-second-dotty-milestone-release.md

@@ -291,7 +291,7 @@ good the code generated by the Dotty Linker with global analysis disabled:
 ## How can you try it out?
 We ship with tools that help you try out the Dotty platform:
 
-  - [IDE features for Visual Studio Code](https://dotty.epfl.ch/docs/usage/ide-support.html)
+  - [IDE features for Visual Studio Code](https://docs.scala-lang.org/scala3/getting-started.html#using-vscode-with-metals)
   - [sbt support, including retro-compatibility with Scala 2](https://github.com/lampepfl/dotty-example-project)
 
 

docs/_blog/_posts/2017-09-07-third-dotty-milestone-release.md

@@ -44,7 +44,7 @@ This technology preview further improves stability and reliability. Some highlig
 ## How can you try it out?
 We ship with tools that help you try out the Dotty platform:
 
- - [IDE features for Visual Studio Code](https://dotty.epfl.ch/docs/usage/ide-support.html)
+ - [IDE features for Visual Studio Code](https://docs.scala-lang.org/scala3/getting-started.html#using-vscode-with-metals)
  - [sbt support, including retro-compatibility with Scala 2](https://github.com/lampepfl/dotty-example-project)
 
 

docs/_blog/_posts/2017-10-16-fourth-dotty-milestone-release.md

@@ -36,8 +36,7 @@ The [new REPL](https://github.com/lampepfl/dotty/pull/2991) instead works by
 manipulating ASTs (Abstract Syntax Trees), this is more robust and will make it
 easier to develop new features: we have already implemented auto-completion
 support (by reusing the APIs we had created for
-the [Dotty IDE](https://dotty.epfl.ch/docs/usage/ide-support.html)) and we have
-plans for displaying API documentation in the REPL.
+the Dotty IDE and we have plans for displaying API documentation in the REPL.
 
 Note that the user interface of the REPL has not changed: like in the old REPL
 we use code adapted from the [Ammonite REPL](http://ammonite.io/#Ammonite-REPL)
@@ -77,7 +76,7 @@ using Dotty with sbt, see the
 
 ### IDE support
 It is very easy to start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 
 ### Standalone installation

docs/_blog/_posts/2017-12-01-fifth-dotty-milestone-release.md

@@ -138,7 +138,7 @@ using Dotty with sbt, see the
 
 ### IDE support
 It is very easy to start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 
 ### Standalone installation

docs/_blog/_posts/2018-03-05-seventh-dotty-milestone-release.md

@@ -114,7 +114,7 @@ local and imported definitions. Members completions take possible implicit conve
 
 We also improved the `find references` functionality. It is more robust and much faster!
 
-Try it out in [Visual Studio Code](https://dotty.epfl.ch/docs/usage/ide-support.html)!
+Try it out in [Visual Studio Code](https://docs.scala-lang.org/scala3/getting-started.html#using-vscode-with-metals)!
 
 ### Better and safer types in pattern matching (improved GADT support)
 
@@ -204,7 +204,7 @@ using Dotty with sbt, see the
 
 ### IDE support
 It is very easy to start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 
 ### Standalone installation

docs/_blog/_posts/2018-04-27-eighth-dotty-milestone-release.md

@@ -133,7 +133,7 @@ using Dotty with sbt, see the
 
 ### IDE support
 It is very easy to start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 
 ### Standalone installation

docs/_blog/_posts/2018-07-06-ninth-dotty-milestone-release.md

@@ -117,7 +117,7 @@ using Dotty with sbt, see the
 
 ### IDE support
 Start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 
 ### Standalone installation

docs/_blog/_posts/2018-10-10-10th-dotty-milestone-release.md

@@ -154,7 +154,7 @@ using Dotty with Mill, see the
 ### IDE support
 
 Start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 ### Standalone installation
 

docs/_blog/_posts/2018-11-30-11th-dotty-milestone-release.md

@@ -140,7 +140,7 @@ using Dotty with Mill, see the
 ### IDE support
 
 Start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 ### Standalone installation
 

docs/_blog/_posts/2019-01-21-12th-dotty-milestone-release.md

@@ -131,7 +131,7 @@ using Dotty with Mill, see the
 ### IDE support
 
 Start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 ### Standalone installation
 

docs/_blog/_posts/2019-03-05-13th-dotty-milestone-release.md

@@ -354,7 +354,7 @@ using Dotty with Mill, see the
 ## IDE support
 
 Start using the Dotty IDE in any Dotty project by following
-the [IDE guide](https://dotty.epfl.ch/docs/usage/ide-support.html).
+the IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html).
 
 ## Standalone installation
 

docs/_docs/contributing/debug-tests.md

@@ -38,7 +38,7 @@ You can run `help` for commands that supported by JDB.
 
 Following file (`tests/debug/while.scala`) is an example of annotated source code:
 
-```Scala
+```scala
 object Test {
 
   def main(args: Array[String]): Unit = {

docs/_docs/contributing/testing.md

@@ -131,12 +131,9 @@ $ sbt
 
 When the sources of a test consist of multiple source files places in a single directory they are passed to the compiler in a single run and the compiler decides in which order to compile them. In some cases, however, to reproduce a specific test scenario it might be necessary to compile the source files in several steps in a specified order. To achieve that one can add a `_${step_index}` suffix to a file name (before the `.scala` or `.java` extension) indicating the order of compilation. E.g. if the test directory contains files named `Foo_1.scala`, `Bar_2.scala` and `Baz_2.scala` then `Foo_1.scala` will be compiled first and after that `Bar_2.scala` together with `Baz_2.scala`.
 
-There are also other suffixes indicating how some particular files are compiled:
-* `_c${compilerVersion}` - compile a file with a specific version of the compiler instead of the one developed on the current branch
-  (e.g. `Foo_c3.0.2.scala`)
-* `_r${release}` - compile a file with a given value of `-scala-output-version` flag (e.g. `Foo_r3.0.scala`)
+The other kind of suffix that can modify how particular files are compiled is `_c${compilerVersion}`. When specified, the file will be compiled with a specific version of the compiler instead of the one developed on the current branch.
 
-Different suffixes can be mixed together (their order is not important although consistency is advised), e.g. `Foo_1_r3.0`, `Bar_2_c3.0.2`.
+Different suffixes can be mixed together (their order is not important although consistency is advised), e.g. `Foo_1_c3.0.2`, `Bar_2_c3.1.0`.
 
 ### Bootstrapped-only tests
 

docs/_docs/contributing/tools/ide.md

@@ -4,8 +4,8 @@ title: Using an IDE
 ---
 
 You can use either Metals (VS Code, vim) or IntelliJ IDEA as described on the
-[IDE Support](../../usage/ide-support.md) page to work on the Scala 3 codebase. There are however
-a few additional considerations to take into account.
+IDE sections of the [getting-started page](https://docs.scala-lang.org/scala3/getting-started.html) to work
+on the Scala 3 codebase. There are however a few additional considerations to take into account.
 
 
 ## Bootstrapping Projects
@@ -25,8 +25,8 @@ These duplicated projects can be confusing and cause issues in IDEs.
 
 When using Metals, the `-bootstrapped` projects are not exported.
 
-In IntelliJ IDEA, we recommend importing the dotty codebase through BSP as described on the
-[IDE Support page](../../usage/ide-support.md), then the `-bootstrapped` projects are not exported.
+In IntelliJ IDEA, we recommend importing the dotty codebase through BSP, then the `-bootstrapped`
+projects are not exported.
 
 
 ## Scala Version warning in Metals

docs/_docs/index.md

@@ -1,6 +1,7 @@
 ---
 layout: index
 redirectFrom: /docs/index.html
+movedTo: https://docs.scala-lang.org/scala3/reference/
 ---
 
 Dotty is the project name for technologies that are considered for inclusion in Scala 3. Scala has
@@ -15,4 +16,3 @@ be a big step towards realizing the full potential of these ideas. Its main obje
 
 In this documentation you will find information on how to use the Dotty compiler on your machine,
 navigate through the code, setup Dotty with your favorite IDE and more!
-

docs/_docs/internals/backend.md

@@ -3,11 +3,11 @@ layout: doc-page
 title: "Backend Internals"
 ---
 
-The code for the backend is split up by functionality and assembled in the
-object `GenBCode`.
+The code for the JVM backend is split up by functionality and assembled in
+`GenBCode.scala`. This file defines class `GenBCode`, the compiler phase.
 
 ```
-object GenBCode    --- [defines] -->        PlainClassBuilder       GenBCode also defines class BCodePhase, the compiler phase
+class GenBCodePipeline -[defines]-->        PlainClassBuilder
      |                                              |
  [extends]                                      [extends]
      |                                              |
@@ -18,34 +18,37 @@ BCodeBodyBuilder   ---------------->        PlainBodyBuilder
 BCodeSkelBuilder   ---------------->        PlainSkelBuilder
      |                                       /      |       \
  BCodeHelpers      ---------------->  BCClassGen BCAnnotGen ...  (more components)
-     |      \       \
-     |       \       \------------->  helper methods
-     |        \       \------------>  JMirrorBuilder, JBeanInfoBuilder (uses some components, e.g. BCInnerClassGen)
-     |         \
+     |    |         \
+     |    |          \------------->  helper methods
+     |    |           \------------>  JMirrorBuilder, JBeanInfoBuilder (uses some components, e.g. BCInnerClassGen)
+     |    |
      |   BytecodeWriters  --------->        methods and classes to write byte code files
      |
- BCodeTypes        ---------------->        maps and fields for common BTypes, class Tracked, methods to collect information on classes, tests for BTypes (conforms), ...
-     |
 BCodeIdiomatic     ---------------->        utilities for code generation, e.g. genPrimitiveArithmetic
-     |
-  BCodeGlue        ---------------->        BType class, predefined BTypes
+                    \-------------->        `bTypes`: maps and fields for common BTypes
 ```
 
+The `BTypes.scala` class contains the `BType` class and predefined BTypes
+
 ### Data Flow ###
-Compiler creates a `BCodePhase`, calls `runOn(compilationUnits)`.
+Compiler creates a `GenBCode` `Phase`, calls `runOn(compilationUnits)`,
+which calls `run(context)`. This:
 
-* initializes fields of `GenBCode` defined in `BCodeTypes` (BType maps,
-  common BTypes like `StringReference`)
-* initialize `primitives` map defined in `scalaPrimitives` (maps primitive
+* initializes `myPrimitives` defined in `DottyPrimitives` (maps primitive
   members, like `int.+`, to bytecode instructions)
-* creates `BytecodeWriter`, `JMirrorBuilder` and `JBeanInfoBuilder` instances
-  (on each compiler run)
+* creates a `GenBCodePipeline` and calls `run(tree)`
+
+`GenBCodePipeline` now:
+
+* initializes the `bTypes` field of `GenBCodePipeline` defined in `BCodeIdiomatic`
+  (BType maps, common BTypes like `StringRef`)
+* creates `BytecodeWriter` and `JMirrorBuilder` instances (on each compiler run)
 * `buildAndSendToDisk(units)`: uses work queues, see below.
-  - `BCodePhase.addToQ1` adds class trees to `q1`
-  - `Worker1.visit` creates ASM `ClassNodes`, adds to `q2`. It creates one
+  - `GenBCodePipeline.feedPipeline1` adds ClassDefs to `q1`
+  - `Worker1.run` creates ASM `ClassNodes`, adds to `q2`. It creates one
     `PlainClassBuilder` for each compilation unit.
-  - `Worker2.addToQ3` adds byte arrays (one for each class) to `q3`
-  - `BCodePhase.drainQ3` writes byte arrays to disk
+  - `Worker2.run` adds byte arrays (one for each class) to `q3`
+  - `GenBCodePipeline.drainQ3` writes byte arrays to disk
 
 
 ### Architecture ###
@@ -110,7 +113,7 @@ To understand how it's built, see:
 final def exemplar(csym0: Symbol): Tracked = { ... }
 ```
 
-Details in `BCodeTypes.scala`
+Details in `BTypes.scala`
 
 #### (e) More "high-level" utilities for bytecode emission ####
 In the spirit of `BCodeIdiomatic`, utilities are added in `BCodeHelpers` for

docs/_docs/internals/coverage.md

@@ -0,0 +1,37 @@
+---
+layout: doc-page
+title: "Code Coverage for Scala 3"
+---
+
+## Instrument code for coverage analysis
+
+[PR#13880](https://github.com/lampepfl/dotty/pull/13880) has implemented code coverage support for Dotty.
+In general, code coverage "instruments" the program at compile time: code is inserted to record which statement are called. This does not change the behavior of the program. Also, a list of all the coverable statements is produced.
+
+To use this feature, add the compile option `-coverage-out:DIR`, where `DIR` is the destination of the measurement files.
+
+You can also set `-sourceroot:PATHS_ROOT` to customize how the path of your source files are resolved.
+Note that `-sourceroot` also sets the root path of the SemanticDB files.
+
+## Details: how the code is instrumented
+
+When the `-coverage-out` option is set, a new phase `instrumentCoverage` runs, just before `firstTransform`.
+For a carefully selected list of tree types, it adds a call to `scala.runtime.Invoker.invoked(statementId, DIR)`.
+
+For instance, this code:
+```
+def method() =
+  println(f())
+```
+
+with `-coverage-out:target/cov` be turned to
+```
+def method() =
+  Invoker.invoked(2, "target/cov")
+  println({
+    Invoker.invoked(1, "target/cov")
+    f()
+  })
+```
+
+At the end of the phase, the list of all the instrumented statements is serialized to the file `DIR/scoverage.coverage`.