From 5e1d24e86332f3eaddc0ed6b04db11bfd0aa0727 Mon Sep 17 00:00:00 2001 From: Lorenzo Gabriele Date: Wed, 9 Jun 2021 11:30:17 +0200 Subject: [PATCH] Fix typo in 3.0.1-RC1 release notes --- docs/blog/_posts/2021-06-07-scala3.0.1-rc1-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/_posts/2021-06-07-scala3.0.1-rc1-release.md b/docs/blog/_posts/2021-06-07-scala3.0.1-rc1-release.md index f635ceadf0ed..d4b7ef88df41 100644 --- a/docs/blog/_posts/2021-06-07-scala3.0.1-rc1-release.md +++ b/docs/blog/_posts/2021-06-07-scala3.0.1-rc1-release.md @@ -19,7 +19,7 @@ With this release, we are introducing a restriction on [features marked as exper The spirit of this policy is to make sure that effectively, no library published for Scala 3 contain experimental features. This way, what is experimental can be easily changed and is not subject to the guarantees of the wider language. And, most importantly, the changes to such features would not affect the community *in practice* – the guarantee not achievable if we just announced the policy without implementing a mechanism to enforce it. -Having said that, we still encourage people to play with the experimental features from the `NIGHTLY` compier versions and discuss their findings. Without the curious and adventurous part of the community playing with the new features, there is no way of knowing what they are good for, and no way to decide whether they should be dropped or promoted to a stable feature. +Having said that, we still encourage people to play with the experimental features from the `NIGHTLY` compiler versions and discuss their findings. Without the curious and adventurous part of the community playing with the new features, there is no way of knowing what they are good for, and no way to decide whether they should be dropped or promoted to a stable feature. More about this change you can read in the PR [#12102](https://github.com/lampepfl/dotty/pull/12102).