Fix following training session from the 20th of May 2021
1 unresolved thread
Issues #21 (closed) and #22 (closed) are tackled in this MR.
Merge request reports
Activity
added C++ label
541 605 "\n", 542 606 "It is also important to highlight that while the STL algorithms may provide you efficiency (this library is written by highly skilled engineers after all), this is not its main draw: the algorithms are written to be as generic as possible. The primary reason to use them is to allow you to think at a higher level of abstraction, not to get the fastest possible implementation. So if your ~~intuition~~ benchmarking has shown that the standard library is causing a critical slowdown, you are free to explore classic alternatives such as [loop unrolling](https://en.wikipedia.org/wiki/Loop_unrolling) - that's one of the strength of the language (and the STL itself opens up this possibility directly for some of its construct - you may for instance use your own memory allocator when defining a container). For most purposes however that will not be necessary.\n", 543 607 "\n", 544 "FYI, C++ 20 introduces a completely new way to deal with algorithms, which does not rely on direct use of iterators but instead on a range library. This leads to a syntax which is more akin to what is done in other languages - see for instance this example lifted from this [blog post](https://www.modernescpp.com/index.php/c-20-the-ranges-library):\n" 608 "FYI, C++ 20 introduces a completely new way to deal with algorithms, which does not rely on direct use of iterators but instead on a range library. This leads to a syntax which is more akin to what is done in other languages (see [@ Coliru](https://coliru.stacked-crooked.com/a/23b256ac459633ff)):\n" Integrated after taking into account @vrouvrea's remark.
mentioned in issue #21 (closed)
mentioned in issue #22 (closed)
Please register or sign in to reply