News for hackers. Stuff that matters.
Re:Sane C++ Libraries by jeffbee on Saturday January 27, 2024 @07:06PM (#39161149)
In decades of professional C++ experience I have never noted depth of backtrace as a usability issue. Give us an example of how a 100-deep backtrace arises as a consequence of the STL.
Re:Sane C++ Libraries by sfpotter on Saturday January 27, 2024 @07:09PM (#39161171)
"Functional" C++ with deeply nested loops implemented using stuff from <algorithm> and <functional> and lambda.
Re:Sane C++ Libraries by o11c on Saturday January 27, 2024 @09:27PM (#39161969)
Before concepts it was certainly possible, but when it happened you just had to add some extra type assertions to make it clear where the error is.
Re:Sane C++ Libraries by summerlight on Saturday January 27, 2024 @09:30PM (#39161989)
Agreed, at least for STL containers I didn't really have to dig into the implementation for 99.9% of the cases. One or two specific old cases were due to memory corruption, but nowadays address sanitizer should do the job. Of course, a lengthy symbol for heavily templatized functions/classes can sometimes be a problem, but it's a separate issue from stack trace depth.