diff --git a/_sips/minutes/2016-11-29-sip-minutes.md b/_sips/minutes/2016-11-29-sip-minutes.md index 628e76619e..26bd0c9987 100644 --- a/_sips/minutes/2016-11-29-sip-minutes.md +++ b/_sips/minutes/2016-11-29-sip-minutes.md @@ -14,7 +14,7 @@ The following agenda was distributed to attendees: | [SIP-28 and SIP-29 - Inline and meta](https://docs.scala-lang.org/sips/inline-meta.html) | Josh Suereth and Iulian Dragos | Pending | | [SIP-24 - Repeated By Name Parameters](https://docs.scala-lang.org/sips/repeated-byname.html) | Heather Miller | Pending | | [SIP-30 - Static members](https://github.com/scala/docs.scala-lang/pull/491/files) | Adriaan Moors | Pending | -| [SIP-27 - Trailing commas](https://docs.scala-lang.org/sips/completed/trailing-commas.html) |Eugene Burkamo | Accepted | +| [SIP-27 - Trailing commas](https://docs.scala-lang.org/sips/trailing-commas.html) |Eugene Burkamo | Accepted | Jorge Vicente Cantero was the Process Lead and Travis Lee was the secretary. @@ -84,7 +84,7 @@ Sébastien says binary compatibility is also an argument in favor of having expl **Conclusion** There are a lot of edge cases when not using annotations. The authors need time to work on the specifics of the proposal and address the Committee's feedback. We need to think about cases around initialization to simplify it. Why do statics need to go first? Show surprising results. There are different implementation strategies. Is this more like @tailrec or does it change generated code? This is the first review iteration of this proposal. -### [SIP-27: Trailing commas](https://docs.scala-lang.org/sips/completed/trailing-commas.html) +### [SIP-27: Trailing commas](https://docs.scala-lang.org/sips/trailing-commas.html) Dale talks about how we wanted trailing commas for multi-line elements. Should be easy. Need to discuss which parts of the syntax can use trailing commas. There are two variants of the SIP to vote on. The first is _parameters and arguments_. The other variant is _everywhere_ for consistency. Dale implemented the first one. The second one shouldn't be more hard to implement except for tuples. It needs to fail compilation somehow. diff --git a/_sips/minutes/2017-05-08-sip-minutes.md b/_sips/minutes/2017-05-08-sip-minutes.md index bb442b857d..5648993695 100644 --- a/_sips/minutes/2017-05-08-sip-minutes.md +++ b/_sips/minutes/2017-05-08-sip-minutes.md @@ -12,7 +12,7 @@ The following agenda was distributed to attendees: |Topic|Reviewers| Accepted/Rejected | | --- | --- | --- | | [SIP-NN - comonadic-comprehensions](https://docs.scala-lang.org/sips/comonadic-comprehensions.html) | Shimi Bandiel | Rejected | -| [SIP-33 - Match infix & prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html)| Oron Port | Pending | +| [SIP-33 - Match infix & prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html)| Oron Port | Pending | |[Scala Library Changes](https://github.com/scala/scala-dev/issues/323)|Adriaan Moors| Scala-dev proposal | Jorge Vicente Cantero was the Process Lead. @@ -56,7 +56,7 @@ Refers to the paper “Denotation” he linked in a proposal, that is not enough **Conclusion** Proposal discarded unanimously. They will send the feedback to the author. -### [SIP-33 - Match infix & prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +### [SIP-33 - Match infix & prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) Skipped since they are waiting for the prototype from the author of the proposal. diff --git a/_sips/minutes/2017-09-21-sip-minutes.md b/_sips/minutes/2017-09-21-sip-minutes.md index 0545a5ed20..69cd7e28fb 100644 --- a/_sips/minutes/2017-09-21-sip-minutes.md +++ b/_sips/minutes/2017-09-21-sip-minutes.md @@ -13,7 +13,7 @@ The following agenda was distributed to attendees: | --- | --- | --- | | [SIP-NN: Right-Associative By-Name Operators](https://docs.scala-lang.org/sips/right-associative-by-name-operators.html) | Adriaan Moors | Pending | | [SIP-ZZ: Opaque types](https://docs.scala-lang.org/sips/opaque-types.html) | Sébastien Doeraene | Pending | -| [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html)| Josh Suereth | Pending | +| [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html)| Josh Suereth | Pending | |[SIP-28 and SIP-29: Inline meta](https://docs.scala-lang.org/sips/inline-meta.html)|Josh Suereth and Iulian Dragos| Pending | Jorge Vicente Cantero was the Process Lead and Darja Jovanovic as secretary. @@ -83,7 +83,7 @@ Syntax "new" "type" **Conclusion**: The SIP is numbered as "SIP 35" by unanimous vote. The above mentioned should to be addressed for the next meeting. -### [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +### [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) Still waiting on the implementation updates, therefore this item will be discussed in the next SIP Meeting. diff --git a/_sips/minutes/2017-10-24-sip-minutes.md b/_sips/minutes/2017-10-24-sip-minutes.md index 43db3062c7..7cbe327e61 100644 --- a/_sips/minutes/2017-10-24-sip-minutes.md +++ b/_sips/minutes/2017-10-24-sip-minutes.md @@ -13,7 +13,7 @@ The following agenda was distributed to attendees: | --- | --- | --- | | [SIP-34: Right-Associative By-Name Operators](https://docs.scala-lang.org/sips/right-associative-by-name-operators.html) | Adriaan Moors | Accepted | | [SIP-35: Opaque types](https://docs.scala-lang.org/sips/opaque-types.html) | Sébastien Doeraene | Pending | -| [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html)| Josh Suereth | Pending | +| [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html)| Josh Suereth | Pending | |[SIP-28 and SIP-29: Inline meta](https://docs.scala-lang.org/sips/inline-meta.html)|Josh Suereth and Iulian Dragos| Pending | Jorge Vicente Cantero was the Process Lead and Darja Jovanovic as secretary. @@ -62,7 +62,7 @@ They are working on updates, but don't have any to share for this meeting. **Conclusion**: The SIP-35 will be proposed on the agenda once the updates are provided. -### [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +### [SIP-33: Match infix and prefix types to meet expression rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) [YouTube time: 03'12''- 10'04''](https://youtu.be/aIc-o1pcRhw?t=194) **Jorge** introduces the SIP adding that **Oron** provided the implementation for associativity of the infix type, not for the prefix type. **Martin** makes the remark that Dotty does the same thing. He continues by saying he is "skeptical" about *prefix* types, as it seems to be another feature and "a necessary compromise to the mathematical conventions". On the other hand, he believes that once the rules for associativity are fixed then types and terms will be consistent. diff --git a/_sips/minutes/2017-12-06-sip-minutes.md b/_sips/minutes/2017-12-06-sip-minutes.md index deb516c0c2..f639631b4a 100644 --- a/_sips/minutes/2017-12-06-sip-minutes.md +++ b/_sips/minutes/2017-12-06-sip-minutes.md @@ -13,7 +13,7 @@ The following agenda was distributed to attendees: | --- | --- | --- | |Discussion and voting on Miles Sabin (Typelevel representative) joining the Committee | | Accepted |[SIP 23: Literal-based singleton types](https://docs.scala-lang.org/sips/42.type.html) | Adriaan Moors | Accepted -|[SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) | Josh Suereth | Accepted | +|[SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) | Josh Suereth | Accepted | |[SIP-NN: Adding prefix types](https://docs.scala-lang.org/sips/adding-prefix-types.html) | Josh Suereth | Pending | |[SIP-35: Opaque types](https://docs.scala-lang.org/sips/opaque-types.html) | Sébastien Doeraene | Not discussed | |Discussion about the future of Scala 2.13 and 2.14 | | Not discussed | @@ -66,12 +66,12 @@ The Committee members agree the SIP is ready to be voted for, given the track re *See also*: Brief explanation about the "The presence of an upper bound of Singleton on a formal type parameter 3rd point in the SIP [YouTube time 14' to 15'35''](https://www.youtube.com/watch?v=Mhwf15gjL9s) and [YouTube Time 17'42'' to 18'20'']( https://youtu.be/Mhwf15gjL9s?t=1069) -### [SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +### [SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) [YouTube time from 1'34'' - 6'45''](https://youtu.be/Mhwf15gjL9s?t=96) **Jorge** shortly introduces the SIP and notifies the Committee that the author has amended all the changes as per Committee suggestions. The SIP-33 was split in two SIPs as follows: -a) [SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +a) [SIP-33: Priority-based infix type precedence rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) b) [SIP-NN: Adding prefix types](https://docs.scala-lang.org/sips/adding-prefix-types.html) diff --git a/_sips/sips/2014-06-27-42.type.md b/_sips/sips/2014-06-27-42.type.md index 2b5ce23fd5..cf0846b777 100644 --- a/_sips/sips/2014-06-27-42.type.md +++ b/_sips/sips/2014-06-27-42.type.md @@ -562,7 +562,7 @@ areas where follow on work is desirable, and one area where another SIP might im ### Infix and prefix types -[SIP-33 Match Infix and Prefix Types to Meet Expression Rules](https://docs.scala-lang.org/sips/make-types-behave-like-expressions.html) +[SIP-33 Match Infix and Prefix Types to Meet Expression Rules](https://docs.scala-lang.org/sips/priority-based-infix-type-precedence.html) has emerged from the work on refined types and computation over singleton types mentioned in the motivation section above. diff --git a/_sips/sips/2016-07-25-unsigned-integers.md b/_sips/sips/2016-07-25-unsigned-integers.md index a5c91742b6..ef8ecd7bf1 100644 --- a/_sips/sips/2016-07-25-unsigned-integers.md +++ b/_sips/sips/2016-07-25-unsigned-integers.md @@ -589,7 +589,7 @@ ScalaNative. ## Previous discussions and implementations When -[Value Classes (SIP-15)](https://docs.scala-lang.org/sips/completed/value-classes.html) +[Value Classes (SIP-15)](https://docs.scala-lang.org/sips/value-classes.html) were first introduced, the possibility to have new numeric types such as unsigned integers was mentioned as a motivation. Subsequently, several people [came up with implementations](https://groups.google.com/forum/#!topic/scala-sips/xtmUjsY9gTY) diff --git a/_style/declarations.md b/_style/declarations.md index 0696e251d7..ed02e81785 100644 --- a/_style/declarations.md +++ b/_style/declarations.md @@ -16,7 +16,7 @@ next-page: control-structures Class/Object/Trait constructors should be declared all on one line, unless the line becomes "too long" (about 100 characters). In that case, put each constructor argument on its own line with -[trailing commas](https://docs.scala-lang.org/sips/completed/trailing-commas.html#motivation): +[trailing commas](https://docs.scala-lang.org/sips/trailing-commas.html#motivation): class Person(name: String, age: Int) { … @@ -36,7 +36,7 @@ put each constructor argument on its own line with If a class/object/trait extends anything, the same general rule applies, put it on one line unless it goes over about 100 characters, and then put each item on its own line with -[trailing commas](https://docs.scala-lang.org/sips/completed/trailing-commas.html#motivation); +[trailing commas](https://docs.scala-lang.org/sips/trailing-commas.html#motivation); closing parenthesis provides visual separation between constructor arguments and extensions; empty line should be added to further separate extensions from class implementation: