-
Notifications
You must be signed in to change notification settings - Fork 2
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
add testing or at least a demo to this repo #8
Comments
I have found by experiment that it is in fact necessary to do something so that changing the plugin causes code in |
maybe the best thing is actually to put the test code in a separate subproject, rather than try to subvert sbt's usual expectations |
I tried the subproject thing:
but it didn't help |
I see kind-projector does
and so does better-monadic-for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there is advice on this in the “Compiler Plugins 101” slides, but it might as well be in this repo directly, too
@hrhino has suggested using this to test:
the
-Jdummy
thing is an attempt to fool sbt into rebuilding when necessary; it's copied (perhaps cargo-culted) from scala-continuations; I should see whether it is necessary on modern sbt, whether it actually works, and whether there's a better, less kludgey wayThe text was updated successfully, but these errors were encountered: