Comments on: The importance of knowing STL <algorithm>s https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/ Jonathan Boccara's blog Wed, 01 Nov 2017 16:28:04 +0000 hourly 1 https://wordpress.org/?v=6.5.3 By: Jonathan Boccara https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-624 Tue, 31 Oct 2017 11:34:00 +0000 https://www.fluentcpp.com/?p=220#comment-624 In reply to Kuba Sejdak.

Oh yes, thanks for noticing that. I’ve updated the link the up-to-date page now.

]]> By: Kuba Sejdak https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-623 Tue, 31 Oct 2017 09:54:00 +0000 https://www.fluentcpp.com/?p=220#comment-623 Great job Jonathan.
BTW, the link to cppreference algo list is broken.
It changed to http://en.cppreference.com/w/cpp/algorithm.

]]> By: Tom https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-255 Mon, 08 May 2017 23:08:00 +0000 https://www.fluentcpp.com/?p=220#comment-255 In reply to Jonathan Boccara.

Thanks

]]> By: Jonathan Boccara https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-252 Mon, 08 May 2017 14:07:00 +0000 https://www.fluentcpp.com/?p=220#comment-252 In reply to Tom.

It’s not related to operator overloading, but rather to the difference between equality and equivalence. I explain the difference in Custom comparison, equality and equivalence with the STL if you want to hear more about this!

]]> By: Tom https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-248 Sun, 07 May 2017 01:28:00 +0000 https://www.fluentcpp.com/?p=220#comment-248 Very interesting article.
But I have one question : why you use the condition “(!(it2->first first) && !(it->first first))” instead the condition “it2->first == it->first” ?

I feel there is some overloaded operators involved, but it is not clear for me.

]]> By: Vladislav Kaplan https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-133 Tue, 07 Mar 2017 09:54:00 +0000 https://www.fluentcpp.com/?p=220#comment-133 Thank you for sharing this stuff with us

]]> By: Bartlomiej Filipek https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-45 Sat, 07 Jan 2017 15:11:00 +0000 https://www.fluentcpp.com/?p=220#comment-45 In reply to Vishal Oza.

I think I support this thinking. I don’t remember when was the last time I’ve used std::for_each… since we now have range based for loop from C++11.
But in pre C++11 code, with a lot of stl used it might be helpful.

]]> By: Vishal Oza https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-43 Fri, 06 Jan 2017 22:24:00 +0000 https://www.fluentcpp.com/?p=220#comment-43 I would never use std::for_each except for the C++ 17 parallel algorithms parallel_policy and parallel_unsequenced_policy. Before that I would used any other, algorithm or numeric algorithm (both are stored in different header files) the use range-based for loop as they have no direct use of iterators and are built into the language, followed by while loops easy to setup, and finally classic for loops for thing with not defined interators such as tiny-xml structure. I would be interested in how ranges as effect algorithms.

]]> By: Jonathan Boccara https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-41 Thu, 05 Jan 2017 22:51:00 +0000 https://www.fluentcpp.com/?p=220#comment-41 In reply to shmoopty.

Thanks for pointing this out Drew. Typo corrected.
The “using namespace std;” was assumed in that call indeed. This code excerpt meant to make the word copy really stand out to get the point across, but I realize that it wasn’t that clear in the end, and using namespaces is not such a good practice anyway. So added back the std:: namespace to copy.

]]> By: shmoopty https://www.fluentcpp.com/2017/01/05/the-importance-of-knowing-stl-algorithms/#comment-40 Thu, 05 Jan 2017 22:23:00 +0000 https://www.fluentcpp.com/?p=220#comment-40 > Now can you tell what this second piece of code does ?

It lacks the closing parentheses needed to compile.

I’ve certainly made the same typo. STL algorithm calls tend to be dense with parentheses.

Related, is “using namespace std;” assumed in that call?

]]>