Mark reference documentation as nightly

docs/_docs/index.md

@@ -1,6 +1,7 @@
 ---
 layout: index
 redirectFrom: /docs/index.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/
 ---
 
 Dotty is the project name for technologies that are considered for inclusion in Scala 3. Scala has

docs/_docs/reference/changed-features/changed-features.md

@@ -1,7 +1,7 @@
 ---
 layout: index
 title: "Other Changed Features"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features.html
 ---
 
 The following pages document the features that have changed in Scala 3, compared to Scala 2.

docs/_docs/reference/changed-features/compiler-plugins.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Changes in Compiler Plugins"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/compiler-plugins.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/compiler-plugins.html
 ---
 
 Compiler plugins are supported by Dotty (and Scala 3) since 0.9. There are two notable changes

docs/_docs/reference/changed-features/eta-expansion-spec.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Automatic Eta Expansion - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion-spec.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion-spec.html
 ---
 
 ## Motivation

docs/_docs/reference/changed-features/eta-expansion.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Automatic Eta Expansion"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion.html
 ---
 
 The conversion of _methods_ into _functions_ has been improved and happens automatically for methods with one or more parameters.

docs/_docs/reference/changed-features/implicit-conversions-spec.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Implicit Conversions - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions-spec.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions-spec.html
 ---
 
 ## Implementation

docs/_docs/reference/changed-features/implicit-conversions.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Implicit Conversions"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions.html
 ---
 
 An _implicit conversion_, also called _view_, is a conversion that

docs/_docs/reference/changed-features/implicit-resolution.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Changes in Implicit Resolution"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-resolution.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-resolution.html
 ---
 
 This section describes changes to the implicit resolution that apply both to the new `given`s and to the old-style `implicit`s in Scala 3.

docs/_docs/reference/changed-features/imports.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Imports"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/imports.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/imports.html
 ---
 
 The syntax of wildcard and renaming imports (and exports) has changed.

docs/_docs/reference/changed-features/interpolation-escapes.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Escapes in interpolations"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/interpolation-escapes.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/interpolation-escapes.html
 ---
 
 In Scala 2 there is no straightforward way to represent a single quote character `"` in a single quoted interpolation. A `\` character can't be used for that because interpolators themselves decide how to handle escaping, so the parser doesn't know whether the `"` character should be escaped or used as a terminator.

docs/_docs/reference/changed-features/lazy-vals-init.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: Lazy Vals Initialization
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/lazy-vals-init.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/lazy-vals-init.html
 ---
 
 Scala 3 implements [Version 6](https://docs.scala-lang.org/sips/improved-lazy-val-initialization.html#version-6---no-synchronization-on-this-and-concurrent-initialization-of-fields)

docs/_docs/reference/changed-features/main-functions.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Main Methods"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/main-functions.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/main-functions.html
 ---
 
 Scala 3 offers a new way to define programs that can be invoked from the command line:

docs/_docs/reference/changed-features/match-syntax.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Match Expressions"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/match-syntax.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/match-syntax.html
 ---
 
 The syntactical precedence of match expressions has been changed.

docs/_docs/reference/changed-features/numeric-literals.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Numeric Literals"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/numeric-literals.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/numeric-literals.html
 ---
 
 [Document was moved](../experimental/numeric-literals.md)

docs/_docs/reference/changed-features/operators.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Rules for Operators"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/operators.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/operators.html
 ---
 
 The rules for infix operators have changed in some parts:

docs/_docs/reference/changed-features/overload-resolution.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Changes in Overload Resolution"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/overload-resolution.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/overload-resolution.html
 ---
 
 Overload resolution in Scala 3 improves on Scala 2 in three ways.

docs/_docs/reference/changed-features/pattern-bindings.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Pattern Bindings"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/pattern-bindings.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/pattern-bindings.html
 ---
 
 In Scala 2, pattern bindings in `val` definitions and `for` expressions are

docs/_docs/reference/changed-features/pattern-matching.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Option-less pattern matching"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/pattern-matching.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/pattern-matching.html
 ---
 
 The implementation of pattern matching in Scala 3 was greatly simplified compared to Scala 2. From a user perspective, this means that Scala 3 generated patterns are a *lot* easier to debug, as variables all show up in debug modes and positions are correctly preserved.

docs/_docs/reference/changed-features/structural-types-spec.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Programmatic Structural Types - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/structural-types-spec.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/structural-types-spec.html
 ---
 
 ## Syntax

docs/_docs/reference/changed-features/structural-types.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Programmatic Structural Types"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/structural-types.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/structural-types.html
 ---
 
 ## Motivation

docs/_docs/reference/changed-features/type-checking.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Changes in Type Checking"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/type-checking.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/type-checking.html
 ---
 
 *** **TO BE FILLED IN** ***

docs/_docs/reference/changed-features/type-inference.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Changes in Type Inference"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/type-inference.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/type-inference.html
 ---
 
 For more information, see the two presentations

docs/_docs/reference/changed-features/vararg-splices.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Vararg Splices"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/vararg-splices.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/vararg-splices.html
 ---
 
 The syntax of vararg splices in patterns and function arguments has changed. The new syntax uses a postfix `*`,  analogously to how a vararg parameter is declared.

docs/_docs/reference/changed-features/wildcards.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: Wildcard Arguments in Types
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/wildcards.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/changed-features/wildcards.html
 ---
 
 The syntax of wildcard arguments in types has changed from `_` to `?`. Example:

docs/_docs/reference/contextual/by-name-context-parameters.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "By-Name Context Parameters"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/by-name-context-parameters.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/by-name-context-parameters.html
 ---
 
 Context parameters can be declared by-name to avoid a divergent inferred expansion. Example:

docs/_docs/reference/contextual/context-bounds.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Context Bounds"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/context-bounds.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/context-bounds.html
 ---
 
 A context bound is a shorthand for expressing the common pattern of a context parameter that depends on a type parameter. Using a context bound, the `maximum` function of the last section can be written like this:

docs/_docs/reference/contextual/context-functions-spec.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Context Functions - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/context-functions-spec.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/context-functions-spec.html
 ---
 
 ## Syntax

docs/_docs/reference/contextual/context-functions.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Context Functions"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/context-functions.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/context-functions.html
 ---
 
 _Context functions_ are functions with (only) context parameters.

docs/_docs/reference/contextual/contextual.md

@@ -1,7 +1,7 @@
 ---
 layout: index
 title: "Contextual Abstractions"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual.html
 ---
 
 ### Critique of the Status Quo

docs/_docs/reference/contextual/conversions.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Implicit Conversions"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/conversions.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/conversions.html
 ---
 
 Implicit conversions are defined by given instances of the `scala.Conversion` class.

docs/_docs/reference/contextual/derivation-macro.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "How to write a type class `derived` method using macros"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/derivation-macro.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/derivation-macro.html
 ---
 
 In the main [derivation](./derivation.md) documentation page, we explained the

docs/_docs/reference/contextual/derivation.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Type Class Derivation"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/derivation.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/derivation.html
 ---
 
 Type class derivation is a way to automatically generate given instances for type classes which satisfy some simple

docs/_docs/reference/contextual/extension-methods.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Extension Methods"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/extension-methods.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/extension-methods.html
 ---
 
 Extension methods allow one to add methods to a type after the type is defined. Example:

docs/_docs/reference/contextual/given-imports.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Importing Givens"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/given-imports.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/given-imports.html
 ---
 
 A special form of import wildcard selector is used to import given instances. Example:

docs/_docs/reference/contextual/givens.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Given Instances"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/givens.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/givens.html
 ---
 
 Given instances (or, simply, "givens") define "canonical" values of certain types

docs/_docs/reference/contextual/multiversal-equality.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Multiversal Equality"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/multiversal-equality.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/multiversal-equality.html
 ---
 
 Previously, Scala had universal equality: Two values of any types

docs/_docs/reference/contextual/relationship-implicits.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Relationship with Scala 2 Implicits"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/relationship-implicits.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/relationship-implicits.html
 ---
 
 Many, but not all, of the new contextual abstraction features in Scala 3 can be mapped to Scala 2's implicits. This page gives a rundown on the relationships between new and old features.

docs/_docs/reference/contextual/right-associative-extension-methods.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Right-Associative Extension Methods: Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/right-associative-extension-methods.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/right-associative-extension-methods.html
 ---
 
 The most general form of leading parameters of an extension method is as follows:

docs/_docs/reference/contextual/type-classes.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Implementing Type classes"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/type-classes.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/type-classes.html
 ---
 
 A _type class_ is an abstract, parameterized type that lets you add new behavior to any closed data type without using sub-typing. This can be useful in multiple use-cases, for example:

docs/_docs/reference/contextual/using-clauses.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Using Clauses"
-movedTo: https://docs.scala-lang.org/scala3/reference/contextual/using-clauses.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/contextual/using-clauses.html
 ---
 
 Functional programming tends to express most dependencies as simple function parameterization.

docs/_docs/reference/dropped-features/auto-apply.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Dropped: Auto-Application"
-movedTo: https://docs.scala-lang.org/scala3/reference/dropped-features/auto-apply.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/dropped-features/auto-apply.html
 ---
 
 Previously an empty argument list `()` was implicitly inserted when

docs/_docs/reference/dropped-features/class-shadowing-spec.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Dropped: Class Shadowing - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/dropped-features/class-shadowing-spec.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/dropped-features/class-shadowing-spec.html
 ---
 
 Spec diff: in section [5.1.4 Overriding](https://www.scala-lang.org/files/archive/spec/2.13/05-classes-and-objects.html#Overriding), add *M' must not be a class*.

docs/_docs/reference/dropped-features/class-shadowing.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Dropped: Class Shadowing"
-movedTo: https://docs.scala-lang.org/scala3/reference/dropped-features/class-shadowing.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/dropped-features/class-shadowing.html
 ---
 
 Scala 2 so far allowed patterns like this:

docs/_docs/reference/dropped-features/delayed-init.md

@@ -1,7 +1,7 @@
 ---
 layout: doc-page
 title: "Dropped: DelayedInit"
-movedTo: https://docs.scala-lang.org/scala3/reference/dropped-features/delayed-init.html
+nightlyOf: https://docs.scala-lang.org/scala3/reference/dropped-features/delayed-init.html
 ---
 
 The special handling of the [`DelayedInit`](https://scala-lang.org/api/3.x/scala/DelayedInit.html)