> The in-place version of swap is generally discouraged because compilers are smart Isn’t that more because CPUs slow down when there are dependencies between

> The in-place version of swap is generally discouraged because compilers are smart Isn’t that more because CPUs slow down when there are dependencies between instructions? Compilers could (and may even do) fairly easily detect that pattern (like they do with some versions of popcnt. See for example https://langdev.stackexchange.com/questions/3942/what-are-the-ways-compilers-recognize-complex-patterns https://langdev.stackexchange.com/questions/3942/what-are-th..., discussed here in https://news.ycombinator.com/item?id=40987123 https://news.ycombinator.com/item?id=40987123) and compile it to whatever is fastest on the target CPU/in the given context (in some contexts, it can be compiled to nothing, just changing the mapping between local variables and the registers they’re stored in)