Topic: Lambda [and] and [=]
Greetings to all. I can not answer for myself on a question: In what cases it is useful to use [and] and [=] instead of explicit a dial-up of parameters? From pluses I have only one argument - very much laziness to register arguments, but it is an argument so-so since if the lambda uses variables, it already any not the correct lambda, and if their only 1... 4 and to enumerate not a problem. Besides, we completely supervise that happens inside. From [&=] - it is more difficult to trace area of usage of a variable. In a case with and we can casually spoil something on a stack, for example, instead of constant function, can be caused , thus after lambda end is ready predict that has been changed. In a case [=] someone above on a stack creates heavy object for copying and the lambda copies it, too it is bad... And so, who can result arguments for [&=]?