Re: [DISCUSS] Introducing Rust into the Git project
- From
Elijah Newren <newren@gmail.com>
- Date
- Jan 11, 2024, 02:21 UTC
- Message-ID
- <CABPp-BHx=4HPSN4enkHTL7PPnNBsJ1vGWe4Em5imH7HcOcH2PA@mail.gmail.com>
- In-Reply-To
- <008701da442f$b2dfe420$189fac60$@nexbridge.com>
On Wed, Jan 10, 2024 at 5:44 PM <rsbecker@nexbridge.com> wrote:
> > On Wednesday, January 10, 2024 7:59 PM, Elijah Newren wrote:
[...]
Show 9 quoted lines
> >Would you be okay with the following alternative: requiring that all Rust code be > >optional for now? > > > >(In other words, allow you to build with USE_RUST=0, or something like that. And > >then we have both a Rust and a C implementation of anything that is required for > >backward compatibility, while any new Rust-only stuff would not be included in > >your build.) > > To address the immediate above, I assume this means that platform maintainers will be responsible for developing non-portable implementations that duplicate Rust functionality
This doesn't at all sound like what I thought I said. The whole proposal was so that folks like NonStop could continue using Git with no more work than setting USE_RUST=0 at build time.
Why do you feel you'd need to duplicate any functionality?