-
Notifications
You must be signed in to change notification settings - Fork 14
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
Scala 2.13.12 release notes draft #850
Conversation
18ead49
to
9678303
Compare
9678303
to
cb910d9
Compare
Co-authored-by: kenji yoshida <6b656e6a69@gmail.com>
As there is no nit too picky, the git query does not account for co-authorship, which I believe counts for unit contribution and not Lukas also shares a co-authorship credit, but it seems a couple of his PRs are sponsored, so I'm not sure how that adds up. I think it means Lukas takes every one out for biers? |
@som-snytt hmm... yeah, that's not ideal. I would use a more correct automated method if one existed, but I don't think I'm sufficiently motivated to build one myself. |
ba4ea23
to
c9b3621
Compare
this is now live at https://github.com/scala/scala/releases/tag/v2.13.12 It's not too late to make further edits — feel free to continue commenting here. |
per discussion on discord chat, perhaps the item on My first comment was that for override inference, Scala 3 style is desirable, but is not backward-compatible. The user should be aware of the difference; the desirable action is to make the old inferred type explicit (for compatibility) or adjust the warning, if the new behavior is acceptable.
The other example in chat was the access modifiers on case class methods when the constructor is private.
If it's desirable to keep the old access, it would be necessary to write the methods by hand. It would be nice to have these use cases in the release notes. Example
|
@som-snytt maybe you and I could work together (not this week) on documenting In the meantime, though, if you have any suggested edits to the release notes themselves, feel free to go ahead and make them. but let's not add too much. or if we do find we've added too much, let's have a goal of moving it to a more permanent location. |
@som-snytt oh, I guess the broader topic of documenting |
@som-snytt the release notes now have:
I remain interested in properly documenting |
rendered
feedback encouraged
no suggestion too small
let's make this as clear and helpful as it can be