Skip to content

Should we deprecate scala.annotation.elidable? #22754

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

Open
hamzaremmal opened this issue Mar 9, 2025 · 1 comment
Open

Should we deprecate scala.annotation.elidable? #22754

hamzaremmal opened this issue Mar 9, 2025 · 1 comment
Labels
area:annotations area:library Standard library itype:question stat:needs decision Some aspects of this issue need a decision from the maintainance team.

Comments

@hamzaremmal
Copy link
Member

The @elidable annotation is not supported in Scala 3.
When #22043 is ready. Should we move to deprecate that annotation ?

@som-snytt
Copy link
Contributor

som-snytt commented Mar 9, 2025

Its main use case is explicitly superseded by inline. However, is there some other use case? Does anyone use elidable on Scala 2? You'd expect more tickets if it were used in the wild.

(Edit: I suspect there are no such other use cases)
(Also Edit: it sounds like an annotation for elidable effects such as static module initialization.)

@Gedochao Gedochao added the stat:needs decision Some aspects of this issue need a decision from the maintainance team. label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:annotations area:library Standard library itype:question stat:needs decision Some aspects of this issue need a decision from the maintainance team.
Projects
None yet
Development

No branches or pull requests

3 participants