Re: [DISCUSS] Introducing Rust into the Git project
- From
Elijah Newren <newren@gmail.com>
- Date
- Jan 11, 2024, 00:33 UTC
- Message-ID
- <CABPp-BH3sva=CNtx8YFGP4Egyau-hR+7njZPFEd-DRTw91BK2w@mail.gmail.com>
- In-Reply-To
- <b2651b38a4f7edaf1c5ffee72af00e46@manjaro.org>
On Wed, Jan 10, 2024 at 1:57 PM Dragan Simic <dsimic@manjaro.org> wrote:
> > Thus, Git should probably follow the same approach of not converting the > already existing code
I disagree with this. I saw significant performance improvements through converting some existing Git code to Rust. Granted, it was only a small amount of code, but the performance benefits I saw suggested we'd see more by also doing similar conversions elsewhere. (Note that I kept the old C code and then conditionally compiled either Rust or C versions of what I was converting.)
Further, I found a really old bug from this effort as well[1], and I find it extremely unlikely that I would have found that bug otherwise. So, converting to Rust can even improve our existing C code.
>, but frankly, I don't see what would actually be > the "new leafs" written in Rust.
In addition to some of the examples Junio mentioned elsewhere, I think new toplevel commands, like git-replay, would qualify.
[1] Yeah, I really need to dig the patch out and send it in. I'll do so shortly.