-
Notifications
You must be signed in to change notification settings - Fork 1k
Tweak Seq migration guide #1333
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
Conversation
Polling for what names we should use for Seqs: https://www.strawpoll.me/18027945 |
LOL
|
|
||
If you're making a library intended to be used by other programmers, then using `scala.Seq`, `scala.IndexedSeq`, or vararg is going to be a breaking change in the API semantics. For example, if there was a function `def orderFood(order: Seq[Order]): Seq[Food]`, previously the library user would have been able to pass in an array of `Order`, but it won't work for 2.13. | ||
This also has the effect of making the type of varargs parameters immutable sequences, due to [SLS 6.6][], so in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few issues:
- change from plural to singular ("These changes require" => "This [...] has")
- no previous effects were mentioned, so the word "also" is confusing
- unqualified "this" - "this change" would be a little better (this one is rather nitpicky and mostly channeling my high school english teacher)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only change I didn't apply is the "also" part. Do you think it's not obvious to the reader the immediate impact of changing the alias? We can fix this up still.
this is super. (and, I like the decision to not introduce |
No description provided.