{"thread":{"id":"63853","subject":"Re: [PATCH 0/7] RFC: Accelerate xdiff and begin its rustification","startedAt":"2025-07-25T23:53:46Z","lastAt":"2025-07-25T23:53:46Z","messageCount":1,"participants":["Ben Knoble"],"isPatch":true,"patchVersion":1,"patchTotal":7},"messages":[{"id":"522777","messageId":"B3683B69-425A-42D2-AA9B-AEAA34475902@gmail.com","threadId":"63853","inReplyTo":null,"subject":"Re: [PATCH 0/7] RFC: Accelerate xdiff and begin its rustification","fromName":"Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2025-07-25T23:53:34Z","receivedAt":"2025-07-25T23:53:46Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"\n> Le 18 juil. 2025 à 06:15, Christian Brabandt <cb@256bit.org> a écrit :\n> \n> \n>> On Do, 17 Jul 2025, Ezekiel Newren via GitGitGadget wrote:\n>> This series accelerates xdiff by 5-19%.\n>> It also introduces Rust as a hard dependency.\n>> …and it doesn’t yet pass a couple of the github workflows; hints from\n>> Windows experts, and opinions on ambiguous primitives would be appreciated\n>> (see below).\n>> This is just the beginning of many patches that I have to convert portions\n>> of, maybe eventually all of, xdiff to Rust. While working on that\n>> conversion, I found several ways to clarify the code, along with some\n>> optimizations.\n> \n> Just a quick heads-up: We (as in Vim/Neovim) have been using gits xdiff\n> library for use in Vim and Neovim.\n> \n> Is the plan to get rid of xdiffs C source completely and replace it by a\n> Rust implementation?\n\nJust a quick FYI about the other branch of this thread that might be relevant: there should remain at least one place to get a quality pure-C xdiff, but I think Vim getting a Rusty xdiff (or the possibility to “bring your own xdiff”) would be nice.\n\n> \n> Thanks,\n> Chris\n> --\n> Eine gute Stellung ist besser als jede Arbeit.\n"}]}