Update SIPs state

Author: scala-improvement-bot

_sips/sips/binary-api.md

@@ -32,7 +32,7 @@ Currently, the compiler automatically generates accessors for references to priv
 * Changing the implementation of an inline definition can be a binary incompatible change
 * Removing final from a class is a binary incompatible change
 
-You can find more details in [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
+You can find more details in [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
 
 ### Avoid duplication of inline accessors
 
@@ -248,7 +248,7 @@ Using references to `@publicInBinary` in inline code can cause binary incompatib
 ### Add a `@binaryAccessor`
 This annotation would generate an stable accessor. This annotation could be used on `private` definition. It would also mitigate [migration costs](https://gist.github.com/nicolasstucki/003f7293941836b08a0d53dbcb913e3c) for library authors that have published unstable accessors.
 
-* Implementation https://github.com/scala/scala3/pull/16992
+* Implementation https://github.com/lampepfl/dotty/pull/16992
 
 
 ### Make all `private[C]` part of the binary API
@@ -267,9 +267,9 @@ The drawback of this approach is that that we would need to force users to keep
 
 ## Related work
 
-* Initial discussions: [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
-* Initial proof of concept (outdated): [https://github.com/scala/scala3/pull/16992](https://github.com/scala/scala3/pull/16992)
-* Single annotation proof of concept: [https://github.com/scala/scala3/pull/18402](https://github.com/scala/scala3/pull/18402)
+* Initial discussions: [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
+* Initial proof of concept (outdated): [https://github.com/lampepfl/dotty/pull/16992](https://github.com/lampepfl/dotty/pull/16992)
+* Single annotation proof of concept: [https://github.com/lampepfl/dotty/pull/18402](https://github.com/lampepfl/dotty/pull/18402)
 * Community migration analysis: [Gist](https://gist.github.com/nicolasstucki/003f7293941836b08a0d53dbcb913e3c)
 * Kotlin: [PublishedApi](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-published-api/) plays the same role as `@publicInBinary`
   but its interaction with (inline definitions)[https://kotlinlang.org/docs/inline-functions.html#restrictions-for-public-api-inline-functions]

_sips/sips/byname-implicits.md

@@ -39,7 +39,7 @@ the knot" implicitly.
 
 ### Implementation status
 
-Byname implicits have been implemented in [Dotty](https://github.com/scala/scala3/issues/1998)
+Byname implicits have been implemented in [Dotty](https://github.com/lampepfl/dotty/issues/1998)
 with an earlier iteration of the divergence checking algorithm described below. A full
 implementation of this proposal exists as a [pull request](https://github.com/scala/scala/pull/6050)
 relative to the 2.13.x branch of the Lightbend Scala compiler and it is scheduled to be included in
@@ -851,7 +851,7 @@ object Test {
 
 because the path `foo` in `foo.Out` is not stable. Full parity with shapeless's `Lazy` would require
 lazy (rather than byname) implicit parameters (see [this Dotty
-ticket](https://github.com/scala/scala3/issues/3005) for further discussion) and is orthogonal to
+ticket](https://github.com/lampepfl/dotty/issues/3005) for further discussion) and is orthogonal to
 this SIP in that they would drop out of support for lazy parameters more generally, as described in
 [this Scala ticket](https://github.com/scala/bug/issues/240).
 

_sips/sips/clause-interleaving.md

@@ -167,7 +167,7 @@ As discussed above, we may want to consider generalizing class parameter lists a
 
 ## Related work
 * Pre-SIP: [https://contributors.scala-lang.org/t/clause-interweaving-allowing-def-f-t-x-t-u-y-u/5525](https://contributors.scala-lang.org/t/clause-interweaving-allowing-def-f-t-x-t-u-y-u/5525)
-* An implementation of the proposal is available as a pull request at [https://github.com/scala/scala3/pull/14019](https://github.com/scala/scala3/pull/14019)
+* An implementation of the proposal is available as a pull request at [https://github.com/lampepfl/dotty/pull/14019](https://github.com/lampepfl/dotty/pull/14019)
 
 ## FAQ
 Currently empty.

_sips/sips/fewer-braces.md

@@ -131,7 +131,7 @@ If there would be code using these idioms, it can be rewritten quite simply to a
 
 ### Tooling
 
-Since this affects parsing, the scalameta parser and any other parser used in an IDE will also need to be updated. The necessary changes to the Scala 3 parser were made here: https://github.com/scala/scala3/pull/15273/commits. The commit that embodies the core change set is here: https://github.com/scala/scala3/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a.
+Since this affects parsing, the scalameta parser and any other parser used in an IDE will also need to be updated. The necessary changes to the Scala 3 parser were made here: https://github.com/lampepfl/dotty/pull/15273/commits. The commit that embodies the core change set is here: https://github.com/lampepfl/dotty/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a.
 
 ### Handling Edge Cases
 
@@ -288,7 +288,7 @@ This is a tradeoff between conciseness and consistency. In the interest of minim
 
  - Doc page for proposed change: https://dotty.epfl.ch/docs/reference/other-new-features/indentation.html#variant-indentation-marker--for-arguments
 
- - Merged PR implementing the proposal under experimental flag: https://github.com/scala/scala3/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
+ - Merged PR implementing the proposal under experimental flag: https://github.com/lampepfl/dotty/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
 
  - Latest discussion on contributors (there were several before when we discussed indentation in general): https://contributors.scala-lang.org/t/make-fewerbraces-available-outside-snapshot-releases/5024/166
 

_sips/sips/interpolation-quote-escape.md

@@ -129,4 +129,4 @@ proposals.
 [^4]: https://github.com/scala/bug/issues/6476#issuecomment-292412577 "@retronym said: +1 to s"$"". Because it doesn't compile today, we don't risk changing the meaning of existing programs."
 [^5]: https://github.com/Scala/Scala/pull/6953/files#diff-0023b3bfa053fb16603156b785efa7ad ""
 [^6]: https://github.com/Scala/Scala/pull/4308 "SI-6476 Accept escaped quotes in interp strings"
-[^7]: https://github.com/scala/scala3/pull/7486 "PR in scala3"
+[^7]: https://github.com/lampepfl/dotty/pull/7486 "PR in dotty"

_sips/sips/match-types-spec.md

@@ -95,7 +95,7 @@ It is however not possible to guarantee that property for *all* cases, since the
 #### Preamble
 
 Some of the concepts mentioned here are defined in the existing Scala 3 specification draft.
-That draft can be found in the dotty repository at https://github.com/scala/scala3/tree/main/docs/_spec.
+That draft can be found in the dotty repository at https://github.com/lampepfl/dotty/tree/main/docs/_spec.
 It is not rendered anywhere yet, though.
 
 Here are some of the relevant concepts that are perhaps lesser-known:
@@ -573,7 +573,7 @@ Notable prior work related to this proposal includes:
 - [Current reference page for Scala 3 match types](https://dotty.epfl.ch/docs/reference/new-types/match-types.html)
 - [Abstractions for Type-Level Programming](https://infoscience.epfl.ch/record/294024), Olivier Blanvillain, Chapter 4 (Match Types)
 - ["Pre-Sip" discussion in the Contributors forum](https://contributors.scala-lang.org/t/pre-sip-proper-specification-for-match-types/6265) (submitted at the same time as this SIP document)
-- [PR with the proposed implementation](https://github.com/scala/scala3/pull/18262)
+- [PR with the proposed implementation](https://github.com/lampepfl/dotty/pull/18262)
 
 ## FAQ
 

_sips/sips/multi-source-extension-overloads.md

@@ -226,7 +226,7 @@ A number of alternatives were mentioned in [the Contributors thread](https://con
 ## Related work
 
 - [Contributors thread acting as de facto Pre-SIP](https://contributors.scala-lang.org/t/change-shadowing-mechanism-of-extension-methods-for-on-par-implicit-class-behavior/5831)
-- [Pull Request in dotty](https://github.com/scala/scala3/pull/17050) to support it under an experimental import
+- [Pull Request in dotty](https://github.com/lampepfl/dotty/pull/17050) to support it under an experimental import
 
 ## FAQ
 

_sips/sips/polymorphic-eta-expansion.md

@@ -420,7 +420,7 @@ No other alternatives have been imagined, the similarity between this proposal a
 - If there is already a proof-of-concept implementation, a link to it will be welcome here. -->
 
 * Pre-SIP: https://contributors.scala-lang.org/t/polymorphic-eta-expansion/5516
-* A naive implementation can be found at https://github.com/scala/scala3/pull/14015 (it is more general than this proposal and thus breaks compatibility)
+* A naive implementation can be found at https://github.com/lampepfl/dotty/pull/14015 (it is more general than this proposal and thus breaks compatibility)
 * A compatibility-preserving implementation is in development.
 
 

_sips/sips/priority-based-infix-type-precedence.md

@@ -137,7 +137,7 @@ However, it is very unlikely that such interaction would occur.
 
 **Related Issues**
 
-* [Dotty Issue #1961](https://github.com/scala/scala3/issues/1961)
+* [Dotty Issue #1961](https://github.com/lampepfl/dotty/issues/1961)
 
 
 ## Backward Compatibility

_sips/sips/quote-pattern-type-variable-syntax.md

@@ -59,11 +59,11 @@ We want to be able to set the bounds of type variables to be able to match again
 ```scala
 case '[ head *: tail ] => h[tail]
 ```
-See [https://github.com/scala/scala3/issues/11738](https://github.com/scala/scala3/issues/11738).
+See [https://github.com/lampepfl/dotty/issues/11738](https://github.com/lampepfl/dotty/issues/11738).
 
 ### Support matching on any kind of type
 We want to match against higher-kinded (or `AnyKind`) types. This is not possible due to the default upper bound of `Any`.
-See [https://github.com/scala/scala3/issues/10864](https://github.com/scala/scala3/issues/10864).
+See [https://github.com/lampepfl/dotty/issues/10864](https://github.com/lampepfl/dotty/issues/10864).
 
 ### Support multiple references to the same type in quoted type patterns
 We want to be able to match using several references to the same type variable.
@@ -135,7 +135,7 @@ TASTy only contains explicit type variable definitions, and this encoding would
 
 ## Related work
 
-* Proof of concept of type variable syntax: [https://github.com/scala/scala3/pull/16910](https://github.com/scala/scala3/pull/16910)
-* Proof of concept of backticks (only interested in the first bullet point): [https://github.com/scala/scala3/pull/16935](https://github.com/scala/scala3/pull/16935)
+* Proof of concept of type variable syntax: [https://github.com/lampepfl/dotty/pull/16910](https://github.com/lampepfl/dotty/pull/16910)
+* Proof of concept of backticks (only interested in the first bullet point): [https://github.com/lampepfl/dotty/pull/16935](https://github.com/lampepfl/dotty/pull/16935)
 
 <!-- ## FAQ -->

_sips/sips/trait-parameters.md

@@ -69,4 +69,4 @@ the evaluation order would be `e1`, initializer of `T`, `e2`, initializer of `V`
 
 ## See Also ##
 
-[Dotty Issue #640](https://github.com/scala/scala3/issues/640)
+[Dotty Issue #640](https://github.com/lampepfl/dotty/issues/640)