I wonder if a successful, albeit slower, approach would be to walk the git commit history in lockstep, applying the behavioral intent behind each commit. If they did this, I would be interested in knowing if they were able to skip certain bug fix commits because the Rust implementation sidestepped the problem.

▲

nicce an hour ago | parent | next [-]

Many segfaults in Bun issue tracker. I bet it would sidestep many.

▲

kajaktum an hour ago | parent [-]

Well…there would still be panics.

	▲	dathinab 27 minutes ago \| parent [-]
		most unsafe language to rust transpilations produce not just pretty terrible rust code but also use unsafe everywhere which is needed, as making things safe often requires refactoring not localized to a single function/code block and doing that while transpiling isn't the best idea. In general I would recommencement a non LLM based transpilation (if possible) and then use an LLM to do bit by bit as localized as possible bottom up refactoring to get ride of unsafe code potentially at some runtime performance cost, followed by another top down refactoring to make thing nice and fast. And human supervision to spot parts where paradigms clash so hard that you have to do some larger changes already during the bottom up step. anyways that means segfaults likely would stay segfaults in the initial transpilled version

▲

efficax 4 hours ago | parent | prev | next [-]

this is an interesting idea and i might try it with something smaller. there are more than 15,000 commits to bun, so you’d have to have some sort of way to operate on groups of commits in one prompt to get that done without thousands and thousands of api requests

▲

lll-o-lll 4 hours ago | parent | prev [-]

Interesting idea