-
Notifications
You must be signed in to change notification settings - Fork 75
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
Cross compile with the full Scala version #15
Comments
Hi @dragos, sorry I only just saw this issue. It's a good point. So far we haven't had any problems but you're right, the code could change. I'll look into publishing against the full version. |
well, lucky so far :-) |
to expand on that, we do normally recommend that compiler plugins be published against the full Scala version. however, kind-projector is an unusual plugin, in that it runs very early during compilation. that part of the Scala compiler rarely changes. and, using the Scala version would mean additional publishing hassle since it would have to be republished for every Scala minor version, and kind-projector is so basic in the Scala library ecosystem that any delay would be felt downstream, as well. so on the balance, I think the status quo is okay. if a Scala version ever comes out that breaks the plugin, it will almost certainly cause compile-time problems that users' CI will catch (rather than expensive runtime issues), and we can rush out a new plugin version that fixes the problem. |
Closed by #119 |
I wonder why kind-projector is cross compiled using only the major Scala version. AFAIK compiler plugins can access compiler internals, therefore are not subject to any binary compatibility guarantees between (any two) releases.
The text was updated successfully, but these errors were encountered: