> that this made bun worse in any measurable way

Issues on GitHub was mass closed claiming zig is no longer relevant without fixing the real issues.

Whole classes of bugs WERE fixed by moving to rust. wouldn’t that result in mass closures of classes of bugs that were no longer relevant in rust? What would you prefer?

	▲	jdiff 15 hours ago \| parent \| next [-]
		Whole classes of bugs are fixed by safe rust. This is not safe rust. As a line-by-line translation with unsafe forced anywhere necessary to make it compile, this should result in no classes of bugs fixed by moving to rust.
	▲	re-thc a day ago \| parent \| prev [-]
		I would prefer they confirm before closing. It's AI / bot anyway. Instead it's just mass keyword zig = close. The bug can still exist post-port. None of it got "fact-checked". In fact a lot of "feature requests" like npm compatibility related or missing specs etc ALL also got closed for being "zig" because reproduction and suggested solution were of course zig. Again doesn't mean it got "auto fixed".