method1 = (f,n) -> do
return f(n)
end
I think a syntax change such as this may be very problematic.
People would not typically expect this, and even if we, say, assume that this
may be a better syntax for newcomers, it would also be a change for people
who have come adjusted to the syntax without the ->.
I understand your comment about confusion to newcomers, but ruby also embraces
a "more than one way" to think about problems, aka flexibility, so I am not
sure that this can be used as primary means to explain why the above syntax
should be added as such.
It also depends a LOT on the individual style. For example zverok uses a
very different style from, say, my style (I rarely use procs and lambdas
or "functional" composition, for instance).
I am not suggesting that the whole idea may not be good per se, but I am very
sceptical of the cost/benefit situation. I am just not sure if the change is
worth it.