Get familiar with C++

[nike0good]

• [x] https://www.youtube.com/watch?v=eidEEmGLQcU
  • [x] Make Report as comment on this issue
• [x] https://www.youtube.com/watch?v=u5senBJUkPc
  • [x] Make Report as comment on this issue
• [x] https://www.youtube.com/watch?v=YnWhqhNdYyk
  • [x] Make Report as comment on this issue
• [x] https://www.youtube.com/watch?v=1OEu9C51K2A
  • [x] Make Report as comment on this issue
• [x] https://www.youtube.com/watch?v=xnqTKD8uD64
  • [x] Make Report as comment on this issue
• [x] https://www.youtube.com/watch?v=86xWVb4XIyE
  • [x] Make Report as comment on this issue
• [x] Put the link of this issue on a comment of the issue of task 1

[nike0good]

Michael VanLoon “STL Algorithms in Action ”

STL in C++ is useful. By using STL, we spend less time coding and focus on other important things. For instance, by using accumulate(s.begin(),s.end()), which is used for calc the sum of a container, we can save time in writing sth. like:

ll ans=0;
for(auto p:s) ans+=p;
return p;

There are various useful algorithms:

 - sort
 - nth_element
 - rotate(it_fir, it_mid, it_end)
 - slide
 - gather //means gather element with same types together
 - set_difference(a.begin(),a.end(),b.begin(),b.end().back_inserter(new_items)); // return new_items (set of what is exist in $a$ and not exist in $b$ )
 - stable_partition

[nike0good]

T. Winters & H. Wright “All Your Tests are Terrible..."

How to make good tests?

Correctness

• executing real scenarios
• not depend upon known bugs

  Readability

• avoid too much boilerplate or distraction
• enough context
• no advanced test framework feature if it is not necessary

  Completeness

• common inputs, corner cases, outlandish cases
• only tests API behaves properly while it uses that API

  Demonstrability

• not reliance on private/friend/TestOnly method

  Resilience

• avoid flaky tests, brittle tests, test depend on execution ordering, mocks with deep dependence upon underlying API, non-hermetic tests.

[nike0good]

[nike0good]

[nike0good]