News for hackers. Stuff that matters.
Re:Rapidstring: Maybe the fastest string library ever by sevensor on Tuesday July 31, 2018 @09:28PM (#17658910)
Is performance really the first thing we should worry about when it comes to string libraries for C? Given the dismal history of character arrays in C, I'd expect safety to be the first thing on the mind of any library implementer, and the first thing mentioned in the README. Also, the second, third, and fourth things.
Re:Rapidstring: Maybe the fastest string library ever by tonto on Tuesday July 31, 2018 @09:54PM (#17659025)
In what sense would safety be such a high priority for a high performance string library? I found this blog post was good at illustrating why undefined...similar to unsafe...operations exist https://nullprogram.com/blog/2018/07/20/
Re:Rapidstring: Maybe the fastest string library ever by drfuchs on Tuesday July 31, 2018 @10:14PM (#17659116)
And though it’s peculiar that the readme doesn’t mention it, the code is (trying to be) safe, at least when assertions aren’t disabled.