TASTy file was produced by Scala 3.2.0 about scribe

[darkfrog26]

@carueda can you clarify why you can't upgrade to 3.2?

[carueda]

Oops, I forgot I had -Xfatal-warnings in my scalacOptions! -- I'm now good to proceed (with more time to address that warning).

[carueda]

Thanks @darkfrog26 et al –

fyi I just retried building my project with Scala 3.2.1 (and latest scribe, among other updates). I managed to fix issues in my previous attempts with Scala 3.2, and it seems the only remaining one (for me) is related with non-local returns, of which there are several in this project. Too bad this is not just a deprecation warning as indicated in that page:

Deprecated: Nonlocal Returns
Returning from nested anonymous functions has been deprecated, and will produce a warning from version 3.2.

but actually already dropped in 3.2! :(

In summary, thanks all again, I'll close this now. Best regards.

[darkfrog26]

This sucks! I thought the whole point of Scala 3 was compliance, which is why the dependencies are _3 not _3.1. I'm not sure what the best practice is to support 3.1 and 3.2. I'll do a little research and get back to you.

[darkfrog26]

I was going to do a quick new release just for you that is built on 3.1.1, but some of the dependencies I'm relying on also are built on 3.2, so it's not quite so easy. :(

[carueda]

Thanks for the quick replies (already useful) and even offer to create a new release!, really appreciated but not need for the trouble! I faced some issues (scribe unrelated) when just setting Scala to 3.2, apparently not straightforward to solve as I would have expected (yes, dealing with scala versions is such a pain). But I'll revisit this more carefully. (My project is not (yet) open source, unfortunately). Thanks again. Fee free to close this ticket.

[darkfrog26]

Feel free to follow up here with the issues you're facing. I asked about this on the Scala Discord channel, which is why you'll see a few people watching the comment above about the issues upgrading to 3.2.