From b78150d0ef7da350b580232f1b80433f34392774 Mon Sep 17 00:00:00 2001 From: Martin Odersky Date: Wed, 7 Dec 2016 14:39:55 +0100 Subject: Add conclusion to blog post --- docs/blog/_posts/2016-12-05-implicit-function-types.md | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs') diff --git a/docs/blog/_posts/2016-12-05-implicit-function-types.md b/docs/blog/_posts/2016-12-05-implicit-function-types.md index 007665564..73e048369 100644 --- a/docs/blog/_posts/2016-12-05-implicit-function-types.md +++ b/docs/blog/_posts/2016-12-05-implicit-function-types.md @@ -358,3 +358,13 @@ comonads is very interesting in its own right. But these discussions will have to wait for another time, as this blog post is already too long. +## Conclusion + +Implicit function types are unique way to abstract over the context in +which some piece of code is run. I believe they will deeply influence +the way we write Scala in the future. They are very powerful +abstractions, in the sense that just declaring a type of a function +will inject certain implicit values into the scope of the function's +implementation. Can this be abused, making code more obscure? +Absolutely, like every other powerful abstraction technique. To keep +your code sane, please keep the (Principle of Least Power)[http://www.lihaoyi.com/post/StrategicScalaStylePrincipleofLeastPower.html] in mind. -- cgit v1.2.3