>> this is seriously going to change my life.
Now I'm curious. Can you give a small code example of the kind of thing this solves and how it will change your life? ;-)
Now I'm curious. Can you give a small code example of the kind of thing this solves and how it will change your life? ;-)
nest_.Hatch([&, &commit = commit, &issued = issued, &nonce = nonce, &v = v, &r = r, &s = s, &amount = amount, &ratio = ratio, &start = start, &range = range, &funder = funder, &recipient = recipient, &reveal = reveal, &winner = winner]() noexcept { return [=]() noexcept -> task<void> { try {
And like, at least there I am able to redeclare them in a "natural" way... I also tend to hide lambdas inside of macros to let me build new scope constructs, and if a structured binding happens to float across one of those boundaries I am just screwed and have to declare adapter references in the enclosing scope (which is the same number of name repetitions, but I can't reuse the original name and it uses more boilerplate).
It's kind of weird structured bindings where not captured with [=](){} before, actually. I'm still stuck at C++11 for most of my work so I cannot use structured bindings at all, but I would not have expected to have to write that kind of monstrosity in C++17
What seems really esoteric to me is that the 'Orchid' Ethereum Token has a $737,057,000.00 fully diluted market cap, which I'm struggling to understand: https://etherscan.io/token/0x4575f41308ec1483f3d399aa9a2826d...