News for hackers. Stuff that matters.

A comment on Libc++'s Implementation of std::string. Parent comment

Re:Libc++'s Implementation of std::string by ncmncm on Friday January 31, 2020 @10:06PM (#22208354)
Buggering op[] would be the slowest possible way to get the NUL there. Some of us would have liked for string operations not to be as absolutely slow as can be achieved. Evidently that is a minority preference.

If you think anybody is complaining about the extra space for the NUL, what you are barking up is not even a tree.

[ Parent | on HN ]
Re:Libc++'s Implementation of std::string by braindeath on Friday January 31, 2020 @10:20PM (#22208423)
> Buggering op[] would be the slowest possible way to get the NUL there.

> Evidently that is a minority preference.

What evidence? Pointing out a fact isn't an endorsement.

> If you think anybody is complaining about the extra space for the NUL

Then what exactly are you complaining about? Setting the byte to 0? If not, why are you being so obtuse?

> what you are barking up is not even a tree.

In this thread your tone is repeatedly that of a condescending jerk.

[ Parent | on HN ]
Re:Libc++'s Implementation of std::string by ncmncm on Saturday February 01, 2020 @12:57AM (#22208986)
You have presented your credentials.
[ Parent | on HN ]