Re: My understanding...
The Rust team already manages the integration. The C group shouldn't be doing any extra work on that end (I guess unless they just want to.)
9 publicly visible posts • joined 26 Oct 2023
If Rust was a shortcut or "easier to learn than C", I'm sure we'd have far less people dropping it at their first borrow checker holdup. The Rust forums are 50% "How do I make the borrow checker like me" posts by weight.
In my experience, Rust code is rarely shorter or easier to write than its C counterpart. It takes a lot of discipline to write anything sufficiently worthwhile in it.
Sorry friend, but you drank the Kool-Aid and thought it was fine wine.
My direct report's performance dramatically improved since it was so much easier to shield them from distractions. They worked less (maintained a steady 40), were far more engaged in meetings, and our external partner reviews improved dramatically. This effect was shared across our entire company. We closed our offices across the world and fully committed to WFH.
Whatever you did wrong, I hope you figure it out, or at least stop listening to people who have an interest in their own employees blaming each other.
My goodness, the amount of people who had to write a thesis about this. It's a tongue-in-cheek point that didn't need a thousand paragraphs dedicated to etymologizing every letter. Obviously it's not really proprietary... Duh.
Point being: There are forks of Linux, but none amount to anything more than tuned spins compared to the UNIX landscape of the old days.
(I never check responses, so dear reader, please feel free to nitpick this to death like the OP.)
The last half of the article goes directly into this detail. You might give it another glance and see if you missed that part.
That said, it's uncommon but not so far as to be an edge case in library design. Lots of security and critical function libraries do internal self tests on load or init to make sure it won't give incorrect results or fail completely later-on during run time.