I understand that's standard if you know you broke them, I was imagining a solution to the problem "this is broken and needs to be fixed, preferably quickly, to unblock me, but I don't want to go down the Rust rabbit hole", since by nature, I would not expect most of the R4L maintainers to want to volunteer to do that kind of turnaround time on a consistent basis.
(This might be an unnecessary optimization if they're already planning for that, but speaking personally, I would think a lot of the fixes involved would probably be somewhat mechanical on the R4L side for that kind of breakage, and I also think it would provide something of a "happy path" for maintainers, in terms of perception, to know that they have an "in case of Rust do X" ramp even if in practice it rarely if ever gets exercised...)
> "this is broken and needs to be fixed, preferably quickly, to unblock me
How would Rust breakage block someone who only writes C?
> I would not expect most of the R4L maintainers to want to volunteer to do that kind of turnaround time on a consistent basis.
There's at least six people who are being paid full time to work on Rust for Linux, across a few different companies. I would imagine fixing any breakage is a high priority for them, and since it's part of their job, I'd imagine they'll get it done.
Sure, sorry, I should have described that better.
I understand that's standard if you know you broke them, I was imagining a solution to the problem "this is broken and needs to be fixed, preferably quickly, to unblock me, but I don't want to go down the Rust rabbit hole", since by nature, I would not expect most of the R4L maintainers to want to volunteer to do that kind of turnaround time on a consistent basis.
(This might be an unnecessary optimization if they're already planning for that, but speaking personally, I would think a lot of the fixes involved would probably be somewhat mechanical on the R4L side for that kind of breakage, and I also think it would provide something of a "happy path" for maintainers, in terms of perception, to know that they have an "in case of Rust do X" ramp even if in practice it rarely if ever gets exercised...)
> "this is broken and needs to be fixed, preferably quickly, to unblock me
How would Rust breakage block someone who only writes C?
> I would not expect most of the R4L maintainers to want to volunteer to do that kind of turnaround time on a consistent basis.
There's at least six people who are being paid full time to work on Rust for Linux, across a few different companies. I would imagine fixing any breakage is a high priority for them, and since it's part of their job, I'd imagine they'll get it done.