fixup! Add blog article about import suggestions

Author: julienrf

blog/_posts/2020-05-05-scala-3-import-suggestions.md

@@ -5,11 +5,14 @@ by: Julien Richard-Foy, Scala Center
 title: Import Suggestions in Scala 3
 ---
 
-Scala’s implicits might be at the same time the most distinguished and the most
-controversial feature of the language. There is evidence that working with implicits can be a
-frustrating experience. Thankfully, the Scala 3 compiler will dramatically
-improve the quality of the error messages shown in case of missing implicit so
-that it will be easier to see _where_ an implicit argument could not be inferred
+Implicits let the compiler “write” significant parts of a program for you.
+For instance, the compiler can summon JSON serializers and deserializers for
+a complete type hierarchy.
+
+However, working with implicits can be a difficult experience. Thankfully, the
+Scala 3 compiler dramatically
+improves the quality of the error messages shown in case of missing implicit so
+that it is easier to see _where_ an implicit argument could not be inferred
 by the compiler, and _how_ to fix the problem.
 
 This article shows these improvements in action in concrete examples of code.
@@ -25,8 +28,8 @@ faced?”
 We also saw that 35% of the respondents of the [2019 developer survey] signaled
 that dealing with missing implicits was a main pain point in their daily
 workflow. Furthermore, they signaled that the two most painful issues they had
-when working with implicits were “finding which parameters have been inferred”
-(46%), and “fixing 'implicit not found' errors” (41%). Last but not least, the
+when working with implicits were “finding which parameters have been inferred”,
+and “fixing 'implicit not found' errors”. Last but not least, the
 word that was most mentioned by the respondents to describe their other pain points
 related to implicits is the word “import”.