-
Notifications
You must be signed in to change notification settings - Fork 129
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
Toolkit to support compiler plugins #3134
Comments
No promises. If you care about delivering this in a timely manner, external contribution would be welcome. Additionally, this is a rather large feature, as it'd introduce compiler plugin flags via a toolkit dependency... which would potentially affect the whole tooling ecosystem. |
That's perfectly valid. I'll try to help out.
Under |
This would mean a separate flag for enabling compiler plugins with custom toolkits would be necessary until it goes through SIP. |
I do not think so. SIP46 defined the default scala behavior for everything without |
That's true, but I'd still rather have it behind an experimental opt-in flag, rather than have everyone get those by just enabling Having this behind a flag would also make users get the experimental warning. |
Is your feature request related to a problem? Please describe.
My library is dependent on a compiler plugin. I would like to define a toolkit to house both library and compiler plugin dependencies to simplify the user experience. It's a great general feature that enables library authors that depend on compile plugins to define tiny toolkits to house both definitions.
Describe the solution you'd like
The toolkit feature currently does not support compiler plugins. It would be great if we can have it. Hopefully within the next minor release of official Scala 3.6.0
Describe alternatives you've considered
Automatic mechanism for libraries to declare dependency on compiler plugins and have those automatically enabled.
Additional context
Currently when publishing the toolkit I get:
The text was updated successfully, but these errors were encountered: