"This is another example of C++ arcane syntax" is a direct quote from the book. And a perfect segway for me to speak about how I'm not impressed by C++. It seems there is something called POLA, although I call it least surprise principle. For me, if Ruby is in one extreme (Ruby doesn't surprise, you often can try something and it will work logically), C++ is in the other extreme (always edge cases). I might end up using C++ but I don't like it.
So before commenting on the book, I needed to try to erase my feelings for the language and try to focus on the book.
And I read it until the end, so that I could write my honest opinion.
So I will. I set 3 stars, because 2 stars seemed harsh. But at over 1100 pages plus apendixes, you would expect more. And IMO, you only get a list of features, edge cases, surprisingly a lot about software engineering in general. Do I really want to read about waterfall/spiral models in a 2021 C++ book? Do I need to read about MVC and not in the context of C++ applying design patterns?.
And poor examples. The only running theme is the Spreadsheet Cell, Grid and so on and it is poor. The other examples are mostly Foo/Bar. Or even something along the lines "you would usually do this in this other way but then my example wouldn't make sense".
Again IMO, you don't get a coherent explaining of the language. This setup might be useful as a refence, but not as a tool to really get the language.
Final straw. Try to look for explicit in the index. And get page 438. Which is in the context of templates, not in the usual explicit for constructors. Not even the index.