Skip to content

Backport "Fix #22794: Emit the definition of Arrays.newArray even though it's a primitive." to 3.3 LTS #222

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

Merged
merged 1 commit into from
Apr 8, 2025

Conversation

tgodzik
Copy link

@tgodzik tgodzik commented Apr 7, 2025

Backports scala#22797 to the 3.3.6.

PR submitted by the release tooling.

… it's a primitive.

Until 3.6.x, we used the user-space definition of `Arrays.newArray`
in Scala.js. We changed it to a primitve in
2852168, to match the behavior of
the JVM backend.

However, that had the side effect of not emitting its definition
at all, like other primitives. For backward binary compat reasons,
we do need that definition.

We specifically make an exception for that method, which is now
emitted, even though it is otherwise treated as a primitive.

[Cherry-picked 9c7193a]
@tgodzik tgodzik force-pushed the backport-lts-3.3-22797 branch from 1d8d1c7 to b646238 Compare April 8, 2025 12:02
Base automatically changed from backport-lts-3.3-22487 to lts-3.3 April 8, 2025 17:44
@tgodzik
Copy link
Author

tgodzik commented Apr 8, 2025

No regressions detected in the community build up to backport-lts-3.3-22797.

Reference

@tgodzik tgodzik merged commit f8a1729 into lts-3.3 Apr 8, 2025
22 checks passed
@tgodzik tgodzik deleted the backport-lts-3.3-22797 branch April 8, 2025 17:44
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.

2 participants