Skip to content

Commit 62041ba

Browse files
authored
Merge pull request #3322 from scala/sync-sips
Sync SIPs from scala/improvement-proposals
2 parents d8a0726 + 3b07c8e commit 62041ba

14 files changed

Lines changed: 25 additions & 25 deletions

‎_sips/sips/025-trait-parameters.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,4 +73,4 @@ the evaluation order would be `e1`, initializer of `T`, `e2`, initializer of `V`
7373

7474
## See Also ##
7575

76-
[Dotty Issue #640](https://github.com/lampepfl/dotty/issues/640)
76+
[Dotty Issue #640](https://github.com/scala/scala3/issues/640)

‎_sips/sips/031-byname-implicits.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ the knot" implicitly.
4343

4444
### Implementation status
4545

46-
Byname implicits have been implemented in [Dotty](https://github.com/lampepfl/dotty/issues/1998)
46+
Byname implicits have been implemented in [Dotty](https://github.com/scala/scala3/issues/1998)
4747
with an earlier iteration of the divergence checking algorithm described below. A full
4848
implementation of this proposal exists as a [pull request](https://github.com/scala/scala/pull/6050)
4949
relative to the 2.13.x branch of the Lightbend Scala compiler and it is scheduled to be included in
@@ -855,7 +855,7 @@ object Test {
855855

856856
because the path `foo` in `foo.Out` is not stable. Full parity with shapeless's `Lazy` would require
857857
lazy (rather than byname) implicit parameters (see [this Dotty
858-
ticket](https://github.com/lampepfl/dotty/issues/3005) for further discussion) and is orthogonal to
858+
ticket](https://github.com/scala/scala3/issues/3005) for further discussion) and is orthogonal to
859859
this SIP in that they would drop out of support for lazy parameters more generally, as described in
860860
[this Scala ticket](https://github.com/scala/bug/issues/240).
861861

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ However, it is very unlikely that such interaction would occur.
141141

142142
**Related Issues**
143143

144-
* [Dotty Issue #1961](https://github.com/lampepfl/dotty/issues/1961)
144+
* [Dotty Issue #1961](https://github.com/scala/scala3/issues/1961)
145145

146146

147147
## Backward Compatibility

‎_sips/sips/037-interpolation-quote-escape.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,4 +133,4 @@ proposals.
133133
[^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."
134134
[^5]: https://github.com/Scala/Scala/pull/6953/files#diff-0023b3bfa053fb16603156b785efa7ad ""
135135
[^6]: https://github.com/Scala/Scala/pull/4308 "SI-6476 Accept escaped quotes in interp strings"
136-
[^7]: https://github.com/lampepfl/dotty/pull/7486 "PR in dotty"
136+
[^7]: https://github.com/scala/scala3/pull/7486 "PR in dotty"

‎_sips/sips/044-fewer-braces.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ If there would be code using these idioms, it can be rewritten quite simply to a
135135

136136
### Tooling
137137

138-
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.
138+
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.
139139

140140
### Handling Edge Cases
141141

@@ -292,7 +292,7 @@ This is a tradeoff between conciseness and consistency. In the interest of minim
292292

293293
- Doc page for proposed change: https://nightly.scala-lang.org/docs/reference/other-new-features/indentation.html#variant-indentation-marker--for-arguments
294294

295-
- Merged PR implementing the proposal under experimental flag: https://github.com/lampepfl/dotty/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
295+
- Merged PR implementing the proposal under experimental flag: https://github.com/scala/scala3/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
296296

297297
- 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
298298

‎_sips/sips/047-clause-interleaving.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ As discussed above, we may want to consider generalizing class parameter lists a
171171

172172
## Related work
173173
* 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)
174-
* 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)
174+
* 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)
175175

176176
## FAQ
177177
Currently empty.

‎_sips/sips/049-polymorphic-eta-expansion.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -424,7 +424,7 @@ No other alternatives have been imagined, the similarity between this proposal a
424424
- If there is already a proof-of-concept implementation, a link to it will be welcome here. -->
425425

426426
* Pre-SIP: https://contributors.scala-lang.org/t/polymorphic-eta-expansion/5516
427-
* 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)
427+
* 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)
428428
* A compatibility-preserving implementation is in development.
429429

430430

‎_sips/sips/052-binary-api.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Currently, the compiler automatically generates accessors for references to priv
3737
* Changing the implementation of an inline definition can be a binary incompatible change
3838
* Removing final from a class is a binary incompatible change
3939

40-
You can find more details in [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
40+
You can find more details in [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
4141

4242
### Avoid duplication of inline accessors
4343

@@ -253,7 +253,7 @@ Using references to `@publicInBinary` in inline code can cause binary incompatib
253253
### Add a `@binaryAccessor`
254254
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.
255255

256-
* Implementation https://github.com/lampepfl/dotty/pull/16992
256+
* Implementation https://github.com/scala/scala3/pull/16992
257257

258258

259259
### Make all `private[C]` part of the binary API
@@ -272,9 +272,9 @@ The drawback of this approach is that that we would need to force users to keep
272272

273273
## Related work
274274

275-
* Initial discussions: [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
276-
* Initial proof of concept (outdated): [https://github.com/lampepfl/dotty/pull/16992](https://github.com/lampepfl/dotty/pull/16992)
277-
* Single annotation proof of concept: [https://github.com/lampepfl/dotty/pull/18402](https://github.com/lampepfl/dotty/pull/18402)
275+
* Initial discussions: [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
276+
* Initial proof of concept (outdated): [https://github.com/scala/scala3/pull/16992](https://github.com/scala/scala3/pull/16992)
277+
* Single annotation proof of concept: [https://github.com/scala/scala3/pull/18402](https://github.com/scala/scala3/pull/18402)
278278
* Community migration analysis: [Gist](https://gist.github.com/nicolasstucki/003f7293941836b08a0d53dbcb913e3c)
279279
* Kotlin: [PublishedApi](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-published-api/) plays the same role as `@publicInBinary`
280280
but its interaction with (inline definitions)[https://kotlinlang.org/docs/inline-functions.html#restrictions-for-public-api-inline-functions]

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,11 +65,11 @@ We want to be able to set the bounds of type variables to be able to match again
6565
```scala
6666
case '[ head *: tail ] => h[tail]
6767
```
68-
See [https://github.com/lampepfl/dotty/issues/11738](https://github.com/lampepfl/dotty/issues/11738).
68+
See [https://github.com/scala/scala3/issues/11738](https://github.com/scala/scala3/issues/11738).
6969

7070
### Support matching on any kind of type
7171
We want to match against higher-kinded (or `AnyKind`) types. This is not possible due to the default upper bound of `Any`.
72-
See [https://github.com/lampepfl/dotty/issues/10864](https://github.com/lampepfl/dotty/issues/10864).
72+
See [https://github.com/scala/scala3/issues/10864](https://github.com/scala/scala3/issues/10864).
7373

7474
### Support multiple references to the same type in quoted type patterns
7575
We want to be able to match using several references to the same type variable.
@@ -141,8 +141,8 @@ TASTy only contains explicit type variable definitions, and this encoding would
141141

142142
## Related work
143143

144-
* Proof of concept of type variable syntax: [https://github.com/lampepfl/dotty/pull/16910](https://github.com/lampepfl/dotty/pull/16910)
145-
* 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)
144+
* Proof of concept of type variable syntax: [https://github.com/scala/scala3/pull/16910](https://github.com/scala/scala3/pull/16910)
145+
* 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)
146146
* Implementation: [https://github.com/scala/scala3/pull/17362](https://github.com/scala/scala3/pull/17362)
147147
* Stabilized implementation: [https://github.com/scala/scala3/pull/18574](https://github.com/scala/scala3/pull/18574)
148148

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ A number of alternatives were mentioned in [the Contributors thread](https://con
230230
## Related work
231231

232232
- [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)
233-
- [Pull Request in dotty](https://github.com/lampepfl/dotty/pull/17050) to support it under an experimental import
233+
- [Pull Request in dotty](https://github.com/scala/scala3/pull/17050) to support it under an experimental import
234234

235235
## FAQ
236236

0 commit comments

Comments
 (0)