-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Not so TASTy to 0.11.8? #3231
Comments
Can you show the E.g.
|
Sure. Thanks!
Anyway, for completeness...
Thanks again! |
I can't see any suspicious here. I though, maybe #3221 changed something but I couldn't confirm. Is your repo public or do you have a reproducer I can fiddle with? |
I have wasted your time. I hope not a lot of it. I am very sorry. I ought to have attempted to set up a reproduction for you before reporting the issue. Perhaps I'd have figured it out. The issue appeared not because of any defect in 0.11.8, but because when I thought I was running 0.11.8, I was in fact running 0.11.0! The repo contains an old wrapper script. I installed 0.11.8 system-wide on my machine, and thought
meant I was running 0.11.8. But in fact, I build though a script like #!/bin/bash
./mill -w runBackground serve --verbose So, Using
to upgrade worked fine. The repo is public, but its
to fix
I am very sorry once again for the time you've devoted to this! |
@swaldman Don't worry. Glad you could fix your issue. |
Hi!
My set-up is unusual and inherently fragile, so this is perhaps not a high priority issue. But I thought I'd let you know, for what it's worth!
I have a very simple mill plugin that calls into a Scala 3 library, which is now compiled as Scala 3.3.3.
I have as meta build
mill-build/build.sc
:and under
0.11.7
(and some earlier versions) the setup has worked fine.Under
0.11.8
, I get...I find reasoning about TASTy compatibility a bit opaque.If
0.11.7
could hit Scala3.3.3
compilations TASTy, I'm not quite sure why0.11.8
would be limited to an earlier version.Thanks for any help!
The text was updated successfully, but these errors were encountered: