-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Scala.js: Various JS interop fixes #9767
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
Scala.js: Various JS interop fixes #9767
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, and thank you for opening this PR! 🎉
All contributors have signed the CLA, thank you! ❤️
Commit Messages
We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).
Please stick to these guidelines for commit messages:
- Separate subject from body with a blank line
- When fixing an issue, start your commit message with
Fix #<ISSUE-NBR>:
- Limit the subject line to 72 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line ("Add" instead of "Added")
- Wrap the body at 80 characters
- Use the body to explain what and why vs. how
adapted from https://chris.beams.io/posts/git-commit
Have an awesome day! ☀️
1fb50f4
to
53be258
Compare
… objects. This restores parity with the run-time semantics of Scala 2. When accessing an inner static class or object, we avoid loading the enclosing objects as values. The discrepancy in run-time semantics was introduced as a by-product of scala#1445 The change in `t4859.check` restores it to its previous state, before that PR.
This is a forward port of the back-end changes in the upstream commit scala-js/scala-js@a1a27f2
…ase. This is basically a forward port of the changes in the upstream commit scala-js/scala-js@b2634ea
53be258
to
9584666
Compare
Depends on #9725.