{"id":122025,"date":"2025-02-21T08:22:05","date_gmt":"2025-02-21T06:22:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/linus-torvalds-poyasnil-svoyu-pozicziyu-v-otnoshenii-priyoma-izmenenij-na-rust"},"modified":"2025-02-21T08:22:05","modified_gmt":"2025-02-21T06:22:05","slug":"linus-torvalds-poyasnil-svoyu-pozicziyu-v-otnoshenii-priyoma-izmenenij-na-rust","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/linus-torvalds-poyasnil-svoyu-pozicziyu-v-otnoshenii-priyoma-izmenenij-na-rust","title":{"rendered":"Linus Torvalds explained his position regarding the acceptance of changes to Rust.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Linus Torvalds joined the discussion about the resistance of maintainers to the implementation of Rust in the kernel, explaining that no one is forcing maintainers to learn Rust, use Rust code, or consider the presence of Rust code in the kernel. Maintainers can continue working solely with C code and have no need to interact with Rust. However, such maintainers cannot influence how Rust develops in the kernel; for example, they cannot interfere with the organization of external interactions between Rust code and the code of their subsystem. <\/p>\n
Maintainers who are interested in promoting Rust can be involved in its development and thus gain the ability to influence the construction of Rust bindings and participate in the maintenance of Rust interfaces. Maintainers who do not wish to deal with Rust can remain unconcerned about Rust bindings, but they will not be able to influence their development. <\/p>\n
Thus, a sort of protective barrier forms around developers who only use the C language, shielding them from issues related to Rust and allowing them to avoid engaging with Rust. However, this wall works both ways; if a developer does not want to deal with Rust, they miss the opportunity to influence its advancement. In other words: 'no one is obliged to deal with Rust' does not mean that 'every maintainer can veto any Rust code.' It is assumed that in practice, the division among maintainers will not be so radical, and some will begin to take Rust bindings into account and collaborate with their developers, but without becoming too deeply involved in the process. <\/p>\n
Regarding the situation with the confirmation of Rust bindings over the DMA subsystem, bypassing the maintainer who is trying to block the acceptance of such bindings, Linus criticized Christoph Hellwig's actions. According to Linus, Christoph overstepped his authority and attempted to influence code that did not affect the DMA subsystem, was implemented in a separate subdirectory, and did not impact the code for which Christoph is responsible. Christoph tried to control how the DMA subsystem is used, and his actions can be compared to attempting to ban the use of DMA in a certain driver just because he disliked that driver. The conclusion: although maintainers are responsible for their code, they are not accountable for how and by whom the results of that code are used. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"