I’m nut sure if suggested solution suits well to the scala language, but I encounter the described problem regularly. Not too often though. It arises when I study a library from its usage documentation instead of scaladocs. In certain cases order of evaluation matters much. So I go to REPL, create simple example and test if the library function uses call-by-name semantics. It would be great to distinguish call-by-name without constructing test examples or looking inside the source code. And it would be equally miserable to lost nice DSL syntax method_name { } to create Future, Try and so on.