Skip to content

Conversation

WojciechMazur
Copy link
Contributor

Reverts #19761 in 3.5.0-RC6 as discussed in #21258 and accepted by the core compiler team.

Copy link
Member

@dwijnand dwijnand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this reverted in 3.5.0?

@WojciechMazur
Copy link
Contributor Author

Conclusion from last core meeting:

#19761 will be reverted on every release branch and on the main. Then, we will release a hotfix for the 3.4 line. We will decide what to do with that change before 3.6. We will set up automatic tests to find similar compatibility problems in the future.

@sjrd
Copy link
Member

sjrd commented Jul 25, 2024

In order to elaborate on the motivation for that decision. What came out of discussions is:

  • The new state after the change looks better per se. We probably want it.
  • We definitely revert it in 3.4.x.
  • We don't want to ship it in 3.5.0 "just because it's there already". We want to do so very intentionally.
  • We don't really have time to do it properly (intentionally, with good accompanying doc, perhaps with migration flags/warnings, etc.) for 3.5.0.
  • Therefore we revert in 3.5.x as well, and take the time to do it properly for 3.6.0.
@dwijnand
Copy link
Member

dwijnand commented Jul 25, 2024

Seems like a standard that I don't feel has been equally applied for other improvements, except for the implicit prioritisation changes and change fixes. I wish I could have participated in this decision. But thank you for explaining the motivation.

@WojciechMazur WojciechMazur merged commit 6eac278 into scala:release-3.5.0 Jul 29, 2024
@WojciechMazur WojciechMazur deleted the backport-3.5.0/revert-19761 branch July 29, 2024 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants