Interesting article about move semantics. There might be some patterns in the codebase.

[sixfourtwelve]

I know theres stuff like std::move(bundle_result.error()); here and there that might have performance penalties. Something to be mindful off :)

https://0xghost.dev/blog/std-move-deep-dive/#mistake-1-return-stdmovelocal_var-breaking-the-compilers-best-optimization

[JoelOtter]

Hey, thanks for the link. It's correct that moving stuff on a return can prevent copy elision! Clang is actually pretty proactive in warning about this.

For the case of the error, this is actually required, as our Error type is an alias for a std::unique_ptr and so cannot be copied anyway.