#rust
threaded - newest
Weird cutoff on the title. This is the full sentence:
Announce that Git 3.0 will make Rust a mandatory part of our build infrastructure.
I’m interested to see how this goes. Maybe they could work with the gitoxide devs to see if there’s some work that’s already been done.
Not really sure myself if Git needs to be RiiR, but that’s their call to make I guess.
Why weird? This is the phrasing used for some patches in the change set, and it means the same thing as the long version.
The title makes it sound like writing Rust for git will be mandatory
This, or a runtime dependency on rustc or something, was my initial impression as well. The link clarifies it pretty quickly though.
Once components are written in Rust, working on them will of course, but sure, the “test balloon” itself doesn’t.
Don’t get me wrong, I’m not against any of that, I just don’t get how this variant of the headline could be misleading
Rock on! This is the ideal way to handle this, since it gives everyone plenty of time to work out the kinks.
threaded - newest
Weird cutoff on the title. This is the full sentence:
I’m interested to see how this goes. Maybe they could work with the gitoxide devs to see if there’s some work that’s already been done.
Not really sure myself if Git needs to be RiiR, but that’s their call to make I guess.
Why weird? This is the phrasing used for some patches in the change set, and it means the same thing as the long version.
The title makes it sound like writing Rust for git will be mandatory
This, or a runtime dependency on rustc or something, was my initial impression as well. The link clarifies it pretty quickly though.
Once components are written in Rust, working on them will of course, but sure, the “test balloon” itself doesn’t.
Don’t get me wrong, I’m not against any of that, I just don’t get how this variant of the headline could be misleading
Rock on! This is the ideal way to handle this, since it gives everyone plenty of time to work out the kinks.