Add an article about migration to Scala 3 #1581
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anatoliykmetyuk
suggested changes
Dec 12, 2023
There was a problem hiding this comment.
Thank you @Zelenya! I've left some comments and suggestions.
Co-authored-by: Anatolii Kmetiuk <anatoliikmt@proton.me>
Zelenya
force-pushed
the
migration-to-scala-3
branch
from
cd3dcb4 to
6e01289
Compare
anatoliykmetyuk
suggested changes
Dec 20, 2023
Zelenya
commented
Dec 20, 2023
sjrd
reviewed
Dec 21, 2023
|
|
||
| Before doing any actual personal work, based on the internet discussions, I had an impression that switching to Scala 3 would be quite painful — in practice, it was pretty straightforward. | ||
|
|
||
| In retrospect, our experience was determined by the technology stack and tools that I (and my team) use: microservices, Typelevel stack, VS Code with Metals, and, most importantly, no macros. It might not be as smooth if any of these wasn't the case. |
There was a problem hiding this comment.
You should pick and choose either "I" or "we" throughout the article. I suggest to use "we"/"our team".
There was a problem hiding this comment.
There is I in the beginning to provide context about me and I closer to the end for the tooling context. Mixing we/you because the article is about the subjective experience and generic advice.
I see a single personal I in the plugin section to we that I can change.
Zelenya
force-pushed
the
migration-to-scala-3
branch
from
948cdaf to
6141961
Compare
Co-authored-by: Sébastien Doeraene <sjrdoeraene@gmail.com>
Zelenya
force-pushed
the
migration-to-scala-3
branch
from
6141961 to
1ada5a1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to share my journey from Scala 2 to Scala 3 and discuss migration to Scala 3. We were thinking that this might be helpful to share with a wider audience.
cc @anatoliykmetyuk @darjutak