TECH_B0LT_GENONA Telegram 5709
Rust теперь обязателен для сборки Git 3.0 (когда он выйдет пока не понятно)

https://lore.kernel.org/git/6674eb07df107d786b747ccd6dce4555d36d5d2c.camel@physik.fu-berlin.de/T/

Hi,

this small patch series introduces Rust into the core of Git. This patch series is designed as a test balloon, similar to how we introduced test balloons for C99 features in the past. The goal is threefold:

- Give us some time to experiment with Rust and introduce proper build infrastructure.

- Give distributors time to ease into the new toolchain requirements. Introducing Rust is impossible for some platforms and hard for others.

- Announce that Git 3.0 will make Rust a mandatory part of our build infrastructure.
. . .

I'm mostly splitting out the topic of introducing Rust from the larger series that introduce it into xdiff so that we can focus more on the actual process of introducing Rust into Git and less on the potential features that we want to build on top of it.

В сообщении упоминается xdiff, это параллельный процес в разработке git

Upcoming patches will simplify xdiff, while also porting parts of it to Rust. In preparation, add some stubs and setup the Rust build. For now, it is easier to let cargo build rust and have make or meson merely link against the static library that cargo builds. In line with ongoing libification efforts, use multiple crates to allow more modularity on the Rust side. xdiff is the crate that this series will focus on, but we also introduce the interop crate for future patch series.

https://lore.kernel.org/git/[email protected]/T/#maf899d074287293cee029a688aa5ab14a5613986

Git has historically been written primarily in C, with some shell and Perl. However, C is not memory safe, which makes it more likely that security vulnerabilities or other bugs will be introduced, and it is also more verbose and less ergonomic than other, more modern languages.

One of the most common modern compiled languages which is easily interoperable with C is Rust. It is popular (the most admired language on the 2024 Stack Overflow Developer Survey), efficient, portable, and robust.

Introduce a document laying out the incremental introduction of Rust to Git and provide a detailed rationale for doing so, including the points above. Propose a design for this approach that addresses the needs of downstreams and distributors, as well as contributors.

https://lore.kernel.org/git/[email protected]/T/#mb0f289427a079dd87e67cc7b597e19ed554a0100


В общем https://растпобеда.рф
🤡43🔥8🫡54👎3😁2❤‍🔥1👍1



tgoop.com/tech_b0lt_Genona/5709
Create:
Last Update:

Rust теперь обязателен для сборки Git 3.0 (когда он выйдет пока не понятно)

https://lore.kernel.org/git/6674eb07df107d786b747ccd6dce4555d36d5d2c.camel@physik.fu-berlin.de/T/

Hi,

this small patch series introduces Rust into the core of Git. This patch series is designed as a test balloon, similar to how we introduced test balloons for C99 features in the past. The goal is threefold:

- Give us some time to experiment with Rust and introduce proper build infrastructure.

- Give distributors time to ease into the new toolchain requirements. Introducing Rust is impossible for some platforms and hard for others.

- Announce that Git 3.0 will make Rust a mandatory part of our build infrastructure.
. . .

I'm mostly splitting out the topic of introducing Rust from the larger series that introduce it into xdiff so that we can focus more on the actual process of introducing Rust into Git and less on the potential features that we want to build on top of it.

В сообщении упоминается xdiff, это параллельный процес в разработке git

Upcoming patches will simplify xdiff, while also porting parts of it to Rust. In preparation, add some stubs and setup the Rust build. For now, it is easier to let cargo build rust and have make or meson merely link against the static library that cargo builds. In line with ongoing libification efforts, use multiple crates to allow more modularity on the Rust side. xdiff is the crate that this series will focus on, but we also introduce the interop crate for future patch series.

https://lore.kernel.org/git/[email protected]/T/#maf899d074287293cee029a688aa5ab14a5613986

Git has historically been written primarily in C, with some shell and Perl. However, C is not memory safe, which makes it more likely that security vulnerabilities or other bugs will be introduced, and it is also more verbose and less ergonomic than other, more modern languages.

One of the most common modern compiled languages which is easily interoperable with C is Rust. It is popular (the most admired language on the 2024 Stack Overflow Developer Survey), efficient, portable, and robust.

Introduce a document laying out the incremental introduction of Rust to Git and provide a detailed rationale for doing so, including the points above. Propose a design for this approach that addresses the needs of downstreams and distributors, as well as contributors.

https://lore.kernel.org/git/[email protected]/T/#mb0f289427a079dd87e67cc7b597e19ed554a0100


В общем https://растпобеда.рф

BY Технологический Болт Генона


Share with your friend now:
tgoop.com/tech_b0lt_Genona/5709

View MORE
Open in Telegram


Telegram News

Date: |

Don’t publish new content at nighttime. Since not all users disable notifications for the night, you risk inadvertently disturbing them. Some Telegram Channels content management tips In the “Bear Market Screaming Therapy Group” on Telegram, members are only allowed to post voice notes of themselves screaming. Anything else will result in an instant ban from the group, which currently has about 75 members. 4How to customize a Telegram channel? Commenting about the court's concerns about the spread of false information related to the elections, Minister Fachin noted Brazil is "facing circumstances that could put Brazil's democracy at risk." During the meeting, the information technology secretary at the TSE, Julio Valente, put forward a list of requests the court believes will disinformation.
from us


Telegram Технологический Болт Генона
FROM American