Here are resources that are in my backlog for programming purposes mainly.

  • this stackoverflow post points to this article that explains EXCEPTION HANDLING in C++. in general, exceptions produce more error prone code. Also this article is terrific and explains the pop_back() and back() split for exception safety (“ If that copy construction or copy assignment fails, then the Stack has completed its side effect (the top element has been popped off) but the popped value is now lost forever because it never reached its destination (oops). This is bad news. In effect, it means that any version of Pop that is written to return a temporary like this cannot be made completely exception-safe, because even though the function’s implementation itself may look technically exception-safe, it forces clients of Stack to write exception-unsafe code. More generally, mutator functions should not return T objects by value.”)
  • These videos about algorithms 1, 2, 3.