News for hackers. Stuff that matters.
Re:The memory safety problem isn't bad coders by maxxxxx on Tuesday February 12, 2019 @01:48PM (#19146267)
Not necessarily. The types may just have very long names. In C++ for iterating through STL container auto is a godsend. The types are very straightforward and easy to reason about but just long.

for (auto it = s.begin(); it != s.end(); it++) {

is much easier to write than

for (vector<int>::iterator it = s.begin(); it!=s.end(); it++) {

Re:The memory safety problem isn't bad coders by jschwartzi on Tuesday February 12, 2019 @02:03PM (#19146411)
I try to avoid using STL because it A) throws exceptions, B) has really convoluted type names, and C) dynamically allocates memory. These are all things you avoid in the embedded space.
Re:The memory safety problem isn't bad coders by maxxxxx on Tuesday February 12, 2019 @02:22PM (#19146586)
Makes sense for embedded.
Re:The memory safety problem isn't bad coders by gowld on Tuesday February 12, 2019 @02:51PM (#19146870)
Any use of templates has the same problem, including templates that are used to generate highly efficient static constants and non-branching-at-runtime code.
Re:The memory safety problem isn't bad coders by llukas on Tuesday February 12, 2019 @03:15PM (#19147083)
Example?

Templates (template metaprogramming) help to avoid exceptions. You can check invariants first and jump into efficient code.

Re:The memory safety problem isn't bad coders by llukas on Tuesday February 12, 2019 @03:16PM (#19147094)
or almost like python:

for (auto &element: s){

even better with structured bindings:

for (auto [key, value]: map){