Comment by lelanthran

> A rando submits a C patch that breaks Rust code, a maintainer accepts this patch and then demands that the R4L devs fix the breakage introduced by someone else and reviewed by themselves. The rando who broke the thing isn't around, and the person who reviewed the change takes no responsibility.

Well, firstly, "randos" aren't getting their patches easily accepted anyway.

And secondly, what's the problem with this? You want one of the following options:

1. Everyone who wants to submit a patch also be proficient in Rust,

Or

2. You want the reviewer to also be proficient in Rust

You don't think that's an unnecessary burden for the existing maintainers?

The burden should be on the people who want to introduce the second language.