-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add the 0.22.0-RC1 release article #8145
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
You can try out this version right now, from the comfort of your SBT, by visiting the [home page](https://dotty.epfl.ch/) and scrolling down to the "Create a Dotty Project" section. Enjoy the ride🚀! | ||
|
||
<!--more--> | ||
# New syntax for collective extension methods |
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.
/cc @odersky
|
||
For the discussion, see [PR #7775](https://github.com/lampepfl/dotty/pull/7775). Also see the GitHub [repository](https://github.com/typelevel/kind-projector) of the kind projector Scala 2 plugin for more context. | ||
|
||
# Further improvements to the contextual parameters syntax |
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.
/cc @odersky
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.
contextual -> context
|
||
For the time being, the change is experimental and the old syntax is also supported. For the discussion, see [PR #8017](https://github.com/lampepfl/dotty/pull/8017). You can browse the documentation concerning the new syntax [here](https://dotty.epfl.ch/docs/reference/contextual/motivation-new.html). | ||
|
||
# Semantics of inline parameters changed |
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.
/cc @nicolasstucki
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.
At the end of this section, we should also mention the changes from #8061
|
||
This change was introduced by [PR #8060](https://github.com/lampepfl/dotty/pull/8060/). For more information about the inline capability of Dotty, see [documentation](https://dotty.epfl.ch/docs/reference/metaprogramming/inline.html). | ||
|
||
# Primitive compiletime operations on singleton types |
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.
| Required: (13 : Int) | ||
``` | ||
|
||
This feature is particularly useful for data science applications. In data science, it is very easy to make a linear algebra mistake, multiply matrices of wrong dimensions and get a runtime error – sometimes after a few hours of running the model. Hence compile-time verification of the models has a great potential for saving time. With such a type-level arithmetics, Scala becomes well-positioned to implement such type-safe data science frameworks. |
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.
/cc @biboudis
3faceb5
to
d1e8b18
Compare
d1e8b18
to
00a56f6
Compare
We need to add the changes of #8021 |
@nicolasstucki, see 1d710ca, WDYT? |
cf5bc87
to
f00e09c
Compare
f00e09c
to
ddfbaf1
Compare
Also, I've added the following to the header of the article:
This should enable users to run examples even more easily. However, we should publish the article once Scastie is updated, a good practice anyway. |
At the beginning of all the prior blog articles, there's this text:
In this PR, I've taken the liberty to replace it with:
IMO the previous version of the header doesn't carry much meaning anymore, as the readers of the article are most probably familiar with what Dotty is. Instead, a good thing to do would be to specify some concrete steps for the users to try out Dotty.
TODO