-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Warn when calling synchronized on Predef or on synthetic file objects #17266
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
Comments
This issue was picked for the Issue Spree No. 29 of 18 April 2023 which takes place in a week from now. @mbovel, @jan-pieter, @yawen-guan will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here. |
I had to rebalance the issue spree teams due to some absences. In the end, we will not tackle this issue today. @jan-pieter, I re-assigned you to #12460. |
Related: #17284 |
Background
|
Fixes scala#17266 Co-Authored-By: Dale Wijnand <[email protected]> Co-Authored-By: itielsa <[email protected]>
Please ignore the 2 previous message from the Scala Center bot. Teams for the next spree can be found here: https://airtable.com/shrSni1OItSuErosU/tblLEWc2ISeGHPbsc. Sorry for the spam! |
Consider the following code in
sync.scala
:scala-cli compile -Xprint:typer -Yprint-debug sync.scala
ouputs:C.f., the first
synchronized
is desugared toPredef.synchronized
. This sounds rather confusing.We should probably issue a warning in this case, and also when calling
this.synchronized
from top-level functions.More context in #7713 (comment).
The text was updated successfully, but these errors were encountered: