"If a call supplies any using argument explicitly, given search is not performed for the remaining params in that clause. If a remaining param has a default, that default is used, even if a compatible given is in scope. This behaviour could have been confusing for users and lead to unexpected problems at runtime. The compiler now reports a warning when default argument would be used instead of given defined in the scope."
"This change also adds new flag -Wrecurse-with-default to emit warning when a method calls itself using a default argument instead of forwarding the current value Bump Scala CLI to v1.9.0 Supports the new Scala 3 nightly Maven repository, Can be used to test Scala 3.8 nightly releases, See the Scala CLI changelog for additional details The new Maven repository for Scala 3 nightly releases Scala 3 nightly releases are no longer published to Maven Central, these can now be found in dedicated https://repo.scala-lang.org/artifactory/maven-nightlies repository. sbt 1.11.5 or later users can use a helper function to reference new repository in their builds"
Scala 3.7.3 introduces warnings when an explicit using argument is supplied and remaining parameters fall back to defaults instead of resolving compatible givens in scope, preventing confusing runtime behavior. The compiler adds a -Wrecurse-with-default flag to warn when a method recursively uses a default argument rather than forwarding the current value. Scala CLI is bumped to v1.9.0 with support for the new Scala 3 nightly Maven repository and testing of Scala 3.8 nightly releases. Scala 3 nightly artifacts are moved from Maven Central to https://repo.scala-lang.org/artifactory/maven-nightlies, and sbt 1.11.5+ offers a helper to reference it. Full changes and credits are available in the release notes.
Read at Scala-lang
Unable to calculate read time
Collection
[
|
...
]