strchr relies on null termination and returns a pointer. It's absolutely vulnerable to abuse. There are many CVEs related to the use of strchr.

▲

Joker_vD a day ago | parent [-]

So why do you consider zig's less-than-performant implementation of strchr to be so egregious as to serve as its condemnation while you give glibc a free pass for exactly the same blunder? Why the double standards? In fact, it's even worse with glibc because it's four times as old as zig.

	▲	dleslie a day ago \| parent [-]
		It's not a problem in isolation. And like I said, the c standard string library is generally considered harmful and dangerous; it does not get a pass. And besides the stability issues, their response to Bun was enough to make it clear that it is a user hostile project. I would never trust a vendor that behaved in that manner to a long standing user, financier and advocate.