gistfile1.scala

def x: Int = { println("x()"); 1 }

def a(byName1: => Int, byName2: => Int): Unit = {
      println("a()")
      println(byName1 + byName2)
}

a(x * 2, x * 3)

// output (note when x is actually called):
// a()
// x()
// x()
// 5

// equivalent call in Ruby: a( proc { x * 2 }, proc { x * 3 } )
// but syntax in Ruby is too verbose to actually design APIs like this

// hard to implement in Ruby VM but easy "cheating" could be in method naming
// e.g. a@(x * 2, x * 3) or some other syntax sugar
// it would be ok since: SyntaxError: `@(' is not allowed as an instance variable name
// it might actually be even better because you know what will happen with your parameters
// when you call the method (because of different syntax in method call)

This reminds me of C++ reference type, which I don't like at all.
The semantics of expression should be recognized at a glance.
In that sense, I don't like macros neither.

What do you use name parameter for?