Skip to content

Implement SIP-61 @unroll annotation #21728

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

Closed
bishabosha opened this issue Oct 8, 2024 · 4 comments · Fixed by #21693
Closed

Implement SIP-61 @unroll annotation #21728

bishabosha opened this issue Oct 8, 2024 · 4 comments · Fixed by #21693
Assignees
Milestone

Comments

@bishabosha
Copy link
Member

bishabosha commented Oct 8, 2024

see https://docs.scala-lang.org/sips/unroll-default-arguments.html

PR in progress: #21693

@987Nabil
Copy link

If unroll leaves experimental in a future release, is there a possibility to back port it to Scala 2? As a lib maintainer (zio ecosystem) I see us dropping Scala 2.12 as soon as sbt 2.0 is there.
But I don't see us or other big libs drop 2.13 any time soon.
And it would be really nice if at least for 2.13 unroll would work for Scala 2/3 cross build libs

@tgodzik
Copy link
Contributor

tgodzik commented Apr 20, 2025

I don't think we'll be able to port it to Scala 2, but there is basis of the features in the form of https://github.com/com-lihaoyi/unroll which is already used in some libraries.

@987Nabil
Copy link

@tgodzik I tried it and it fails as reported in com-lihaoyi/unroll#11
I don't know, if @lihaoyi will keep working and fixing bugs on it. But I strongly suggest to find a good solution for this. As a Scala 3 only feature the usage is really limited.

@lihaoyi
Copy link
Contributor

lihaoyi commented Apr 21, 2025

@987Nabil I opened a 300USD bounty on that issue, hopefully someone is able to take a crack at it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants