Rule 4.4 example about scala-best-practices HOT 1 OPEN

Yeah, the example can be simplified.

However I find that the usage of blocking is still valuable as it serves documenting purposes.

Plus usually the thread-pool is injected from somewhere, being a bad idea to hard-code it and so it's often a matter of configuration ... change the thread-pool, then it starts working again. Which is why operations that block are error prone, as their correctness depends on the configuration of the underlying thread-pool. Hence clearly seeing in code things that block is very important.

BTW, Await.result already uses blocking in its implementation. But then you can also see it clearly that it blocks. So an example using Await.result is not the most fortunate. But couldn't think of anything better.

from scala-best-practices.