On Wednesday, January 10, 2024 9:21 PM, Elijah Newren wrote:

On Wed, Jan 10, 2024 at 5:44 PM [off-list ref] wrote:

quoted

On Wednesday, January 10, 2024 7:59 PM, Elijah Newren wrote:

[...]

quoted

quoted

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?

I think I misunderstood. What I took from this is that all new functionality would be in Rust, which would require a custom implementation in C for platforms that did not have Rust available - if that is even practical. Did I get that wrong?