Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync with the stable documentation branch #19828

Open
wants to merge 462 commits into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

This pull request is syncing the main with changes from language-reference-stable.

It was created automatically after 1eac8fb by @Kordyjan

odersky and others added 30 commits January 18, 2024 17:36
Drop the experimental language import. I believe everybody agrees that this
is a desirable improvement, and type inference and implicit search
have traditionally been in the realm of the compiler implementers.

Experimental language imports have to live forever (albeit as deprecated
once the feature is accepted as standard). So they are rather heavyweight
and it is unergonomic to require them for smallish improvements to type
inference.

The new road map is as follows:

 - In 3.4: warning if behavior would change in the future.
 - In 3.5: error if behavior would change in the future
 - In 3.future (at the earliest 3.6): new behavior.
This reverts commit 48e0340.
Synthesized calls for default implicits needed a using clause when the
method was an implicit method, but had a context bound parameter in
3.4-migration.

Also, we can't rewrite adding a `using` clause if the argument list is
empty, since we are lacking precise position info.

Fixes #19506
Attempted small grammar improvements
Attempted small grammar improvements
Added missing import
From MVNRepository:

Direct vulnerabilities:
- CVE-2022-36033

Vulnerabilities from dependencies:
- CVE-2023-26049
- CVE-2023-26048
- CVE-2022-25647

https://mvnrepository.com/artifact/org.jsoup/jsoup/1.14.3
(cherry picked from commit 27fbeaf)
Added missing import
Backport of #19564 to 3.4.z

From MVNRepository:

Direct vulnerabilities:
- CVE-2022-36033

Vulnerabilities from dependencies:
- CVE-2023-26049
- CVE-2023-26048
- CVE-2022-25647

https://mvnrepository.com/artifact/org.jsoup/jsoup/1.14.3

(cherry picked from commit 27fbeaf)
WojciechMazur and others added 30 commits December 10, 2024 15:40
…directory (#22199)

Fixes #22194 

Restores top-level directory `scala3-${version}` that is present in
artifacts published before Scala 3.6, removed during hotfix 3.6.1
release.
We now follow the [Well formed SDK archives
layout](https://github.com/sdkman/sdkman-cli/wiki/Well-formed-SDK-archives).
Removing the top-level directory even though at first glance looked like
an improvement was in fact introducing problems to multiple package
managers and build tools.

[Cherry-picked 5b3d82a]
**Problem**
It wasn't clear what action users was suppose to take to suppress
the new-from-3.6 Given search preference warning.

**Solution**
1. This refactors the code to give the warning an error code E205.
2. In case of warnings, tell the user to choose -source 3.5 vs 3.7,
   or use nowarn annotation.

[Cherry-picked 004cfc5]
Signed-off-by: Rui Chen <[email protected]>

[Cherry-picked 70cc1a1]
…o JLine 3.27.1 (was 3.27.0)" to 3.6 (#22271)

Backports #22205 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
…top-level directory " to 3.6 (#22272)

Backports #22199 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
…22273)

Backports #22189 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
…props are replaced or mutated" to 3.6 (#22275)

Backports #22180 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
Backports #21825 to the 3.6.3.

PR submitted by the release tooling.
Backports #22185 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
… 3.6 (#22277)

Backports #22227 to the 3.6.3.

PR submitted by the release tooling.
[skip ci]
…o 3.6 (#22278)

Backports #22228 to the 3.6.3.

PR submitted by the release tooling.
note that I added "dba Akka" to NOTICE.md but I don't believe it's
necessary to pollute the version history adding that to the top of
every source file, too. in legal contexts, "Lightbend, Inc." is still
the company's legal name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.