Implicit lambda names

[zhelenskiy]

I added some ideas mentioned here.

I think that it is a good idea to write there a summary of this discussion.

Allow any name in single parameter lambda functions

I have an idea of how to get the advantages from a similar syntax without the mentioned disadvantages. You can: Make to use $ before the lambda scope (before {) Make to start the name of the parameter with $ Why this helps: I can not accidentally mix up common captured variables and implicit parameters (now it is insensitive to them) I can guess from such implicit parameter what it is (not like it that can correspond to anything in the world) Syntax is still laconic It is also insensitive…

@HughG this message is for you too, I suppose.