He-Pin opened a new pull request, #1068:
URL: https://github.com/apache/pekko-http/pull/1068

   ## Summary
   
   - Replace `private[this]` with `private` across ~40 files (Scala 3 
deprecation: `private[this]` is subsumed by `private`)
   - Replace `= _` with explicit defaults (`= null`, `= 0L`, etc.) across ~15 
files (Scala 3 deprecation)
   - Fix refutable pattern in `HttpHeaderParserSpec` (`val` type annotation → 
`asInstanceOf`)
   
   ## Details
   
   These are purely mechanical changes to address Scala 3 deprecation warnings. 
No behavioral changes.
   
   ### `private[this]` → `private`
   Affects benchmarks, core engine classes, parsers, model classes, testkit, 
and test code.
   
   ### `= _` → explicit defaults
   Replaces uninitialized var declarations with explicit defaults (`= null` for 
reference types, `= 0L` for longs, etc.).
   
   ### Test fix
   `HttpHeaderParserSpec`: refutable pattern in `val` definition (type 
annotation) replaced with `asInstanceOf`.
   
   ## Test plan
   - [x] `sbt "++ 2.13 Test/compile"` passes
   - [x] `sbt "++ 3.3 Test/compile"` passes
   - [x] No behavioral changes — purely mechanical refactoring
   
   ### Motivation
   Scala 3 deprecates `private[this]` and `= _` syntax. These changes ensure 
forward compatibility.
   
   ### Modification
   Mechanical replacement of deprecated syntax across ~50 files.
   
   ### Result
   All modules compile cleanly on both Scala 2.13.18 and 3.3.8 with no 
deprecation warnings for these patterns.
   
   ### Tests
   - `sbt "++ 2.13 Test/compile"` passes
   - `sbt "++ 3.3 Test/compile"` passes
   
   ### References
   None - Scala 3 forward compatibility


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to