-
Notifications
You must be signed in to change notification settings - Fork 185
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
Publish cli_3 & rules_3, built against core_2.13 #1680
Comments
bjaglin
changed the title
Todos for cross compiling in Scala 3
scala 3: publish scalafix-cli_3
Oct 2, 2022
This was referenced Oct 2, 2022
Closed
This was referenced Oct 2, 2022
5 tasks
2 tasks
9 tasks
bjaglin
changed the title
scala 3: publish scalafix-cli_3
Publish cli/rules/reflect_3, built against core_2.13
Aug 21, 2024
This was referenced Aug 22, 2024
bjaglin
changed the title
Publish cli/rules/reflect_3, built against core_2.13
Publish cli_3 & reflect_3, built against core_2.13
Aug 24, 2024
bjaglin
changed the title
Publish cli_3 & reflect_3, built against core_2.13
Publish cli_3 & rules_3, built against core_2.13
Aug 24, 2024
Done - demonstrated with #2044 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follows https://github.com/rvacaru/GsoC-2022-Scalafix
core_3wait for Migrate quasiquote macros to Scala 3 scalameta/scalameta#3347 acceptable to start without support of quasiquotes and getting 2.13 artifacts in the classpath?we'll proceed with cli_3/reflect_3/rules_3 builtcore_2.13 to unblock ExplicitResultTypes, and follow-up with core_3 in Official support for writing community rules in Scala 3 #2041reflect_3add warning that quasiquotes are not supported and that compiler behavior might be different, proposing a fallback to 2.13 artefacts (or throw an exception that cli understands, which would reboot with 2.13 automatically?)let's stick to reflect_2.13 instead, and follow-up in Official support for writing community rules in Scala 3 #2041do we really need full-cross-version in Scala 3? Consider https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.htmlwe do for ExplicitResultTypes to be efficient for LTS & Next, see feature: ExplicitResultTypes for Scala 3 #2023 (comment)The text was updated successfully, but these errors were encountered: