Reorder NamedTuples with publicInBinary

Author: WojciechMazur

_posts/2025-05-07-release-notes-3.7.0.md

@@ -15,47 +15,10 @@ We're excited to announce the release of Scala 3.7.0 — a significant minor rel
 
 The [Scala Improvement Process (SIP)](https://docs.scala-lang.org/sips/) is how language changes and additions are made.
 
-### [SIP-52: Binary APIs](https://docs.scala-lang.org/sips/binary-api.html)
-
-For library maintainers, Scala 3.7.0 stabilizes the `@publicInBinary` annotation, introduced experimentally in Scala 3.4. This annotation ensures binary compatibility when inline methods access non-public members and prevent generation of redundant accessors required by inlining mechanism.
-
-Inline methods are always inlined at their call sites. If they refer to members not visible outside their defining scope, the compiler generates accessor methods. The accessors are not subject to binary compatibility; they might be emitted differently by newer versions of compiler or eventually removed.
-The `@publicInBinary` annotation addresses this by emitting those members as public in bytecode, while maintaining restricted source-level visibility.
- This allows the compiler to refer to the original non-private member without the need to create additional accessors.
-
-```scala
-object api:
-  class Service:
-    private[api] def implementation(): Unit = println("Executing old API")
-    inline def use() = implementation()
-    // generated by compiler, accessed in `use()`
-    // def api$Service$$inline$implementation(): Unit = implementation()
-  
-  class Consumer:
-    inline def consume() = api.Service().implementation()
-    // generated by compiler, accessed in `consume()`
-    // def inline$implementation$i1(x$0: api$Service) = x$0.implementation()
-    
-    @scala.annotation.publicInBinary
-    private[api] var isActive: Boolean = false
-    inline def isStale = !isActive 
-```
-
-The new annotation also resolves a long-standing issue with the inability to invoke a private constructor of a class from inlined methods. Now by annotating the constructor with `@publicInBinary` you are allowed to access it directly from inlined methods.
-
-```scala
-import scala.annotation.publicInBinary
-
-class Printer @publicInBinary private(id: Int)
-object Printer:
-  inline def create(): Printer = new Printer(42) // Not allowed previously
-```
-
-SIP-52 has also introduced the linting flag `-WunstableInlineAccessors` which detects and emits warnings for all unstable accessors generated for inline methods. This flag has been available since Scala 3.4.0. We highly recommend its usage of users' codebases, especially in the case of public libraries.
 
 ### [SIP-58: Named Tuples](https://docs.scala-lang.org/sips/named-tuples.html)
 
-Named Tuples introduced as experimental in Scala 3.5 are now a stable feature.
+Named Tuples, introduced as experimental in Scala 3.5, are now a stable feature.
 Named tuples are a convenient lightweight way to return multiple results from a function or to model the data using tuples while allowing you to use meaningful names for its fields.
 
 ```scala
@@ -115,6 +78,44 @@ case class Release(version: String, issues: List[String])
   assert(query.issues.isEmpty)
 ```
 
+### [SIP-52: Binary APIs](https://docs.scala-lang.org/sips/binary-api.html)
+
+For library maintainers, Scala 3.7.0 stabilizes the `@publicInBinary` annotation, introduced experimentally in Scala 3.4. This annotation ensures binary compatibility when inline methods access non-public members and prevent generation of redundant accessors required by inlining mechanism.
+
+Inline methods are always inlined at their call sites. If they refer to members not visible outside their defining scope, the compiler generates accessor methods. The accessors are not subject to binary compatibility; they might be emitted differently by newer versions of compiler or eventually removed.
+The `@publicInBinary` annotation addresses this by emitting those members as public in bytecode, while maintaining restricted source-level visibility.
+ This allows the compiler to refer to the original non-private member without the need to create additional accessors.
+
+```scala
+object api:
+  class Service:
+    private[api] def implementation(): Unit = println("Executing old API")
+    inline def use() = implementation()
+    // generated by compiler, accessed in `use()`
+    // def api$Service$$inline$implementation(): Unit = implementation()
+  
+  class Consumer:
+    inline def consume() = api.Service().implementation()
+    // generated by compiler, accessed in `consume()`
+    // def inline$implementation$i1(x$0: api$Service) = x$0.implementation()
+    
+    @scala.annotation.publicInBinary
+    private[api] var isActive: Boolean = false
+    inline def isStale = !isActive 
+```
+
+The new annotation also resolves a long-standing issue with the inability to invoke a private constructor of a class from inlined methods. Now by annotating the constructor with `@publicInBinary` you are allowed to access it directly from inlined methods.
+
+```scala
+import scala.annotation.publicInBinary
+
+class Printer @publicInBinary private(id: Int)
+object Printer:
+  inline def create(): Printer = new Printer(42) // Not allowed previously
+```
+
+SIP-52 has also introduced the linting flag `-WunstableInlineAccessors` which detects and emits warnings for all unstable accessors generated for inline methods. This flag has been available since Scala 3.4.0. We highly recommend its usage of users' codebases, especially in the case of public libraries.
+
 ## Preview features
 
 Scala 3.7 introduces the concept of `preview` features — fully implemented and SIP-approved, but potentially subject to small refinements before becoming stable.