Date: Thu, 20 Apr 2023 10:42:30 +0200 From: Hans Petter Selasky <hselasky@freebsd.org> To: Jessica Clarke <jrtc27@freebsd.org> Cc: Brooks Davis <brooks@freebsd.org>, src-committers <src-committers@freebsd.org>, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: 8dcf3a82c54c - main - libc: Implement bsort(3) a bitonic type of sorting algorithm. Message-ID: <aa51ee4b-39a4-b69f-57f3-7475df035543@freebsd.org> In-Reply-To: <2840BE79-CC25-427A-A5E9-476A38E749E3@freebsd.org> References: <202304191206.33JC6Qcp062380@gitrepo.freebsd.org> <ZEAM3rO9r5e97BHE@spindle.one-eyed-alien.net> <a073fd36-9aa9-e988-0cc5-86af305fb654@freebsd.org> <3B5734C4-8630-4CD5-BA8D-DE33899161F1@freebsd.org> <e2ea5c89-aa48-e257-b9d5-7fe783bf216e@freebsd.org> <2840BE79-CC25-427A-A5E9-476A38E749E3@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/19/23 22:17, Jessica Clarke wrote: > Except they’re not, because all of what bsort provides can be provided > by qsort. All people care about are being able to quickly sort their > data and whether it’s a stable sort. Hi Jessica, From this I'm reading: Going bad being rare should just be accepted, because the benefit is greater than the deficit. I disagree: Bugs like those in FreeBSD's qsort() can/do create random victims out there having real life consequences. Being a victim is fine as long as it is not me? Databases, QuickSort, JSON, HTML, HTTP request timeout, default values and AirTags. What can go wrong goes wrong! --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aa51ee4b-39a4-b69f-57f3-7475df035543>