He explained it so well, it’s amazing. It all makes sense to me now.

This is how it should be done. No silly explanations, just plain magic.

Returning the filter view in that context is unfortunately undefined behavior since the view holds a ref towards the vector passed by copy to the function that will then be dangling. To fix it you should call std::move on nums when applying the pipe operator, that will make the view owner of the vector itself will be moved alongside it when returning from the function.

@cristian-si1gb

7 ай бұрын

Taking the vector by const reference in the function also wouldn't solve the issue because that vector might be a lifetime extension of an external prvalue (depending on how the function was called) and it will once again be dangling...

🤯

“Am I going to explain it? Absolutely not!” 😅

I love/hate these lightning talks (see also "How Fast Are Computers " by Matt Godbolt) because on one hand they're so good and funny but on the other hand they leave me craving 30 more minutes of what I've just watched

Short code != good and clear code.

code_report! love you man!

thank you, I will absolutely not check that black voodoo magic, I pretty much like having a sound mind

When they say lightning, they mean it. The one problem with the example is it should have been random data because with a linear progression there's an even easier solution just copying every other element down by a progressive count up without even checking whether they're even or odd, but data in real life isn't so neat.

A weird idea, this format. Still, I am enticed by BQN. Fantaxis = fantastic syntax. Drink when he says "absolutely not" and "folks".

not a race, guys

“Absolutely not”

BQN is more confusing than primer

Lol