The developers of the Rust programming language are preparing to publish rules for the use of AI assistants in the project. The proposed rules have been refined through discussions totaling over 3,000 messages, approved by 4 maintainers, and are awaiting publication. With certain exceptions, the rules prohibit the submission of AI-generated code to the main rust-lang/rust repository, but do not apply to submodules, branches, and dependencies from the crates.io catalog, as well as other repositories of the organization. The rules allow for the use of AI for code analysis, study, review, and verification.
The use of AI is permitted in cases where information obtained through AI is used privately by a single developer and not shared publicly. For example, when a developer asks AI questions about code, compiles a summary of comments on a PR or issue, engages AI for reviewing changes, creates tools for personal use through AI, or consults with AI on possible solution choices. Creating experimental changes through AI, which are not subject to review by other participants, is also allowed.
The use of AI to generate comments, issue reports, and change descriptions published on behalf of a participant is prohibited. However, quoting outputs from AI is allowed with a clear indication that the content was generated through AI (for example, attaching diagnostic results from AI). Creating documentation through AI is forbidden. During reviews, AI conclusions are not considered sufficient for accepting or rejecting changes — AI verification results are intended for recommendation only.
With stipulations and a clear mention that the result was obtained through AI, the use of AI is permitted for machine translation into other languages, error detection and verification, as well as making minor changes to code and texts (for example, correcting typos and selecting synonyms).
As part of the experiment, the transmission of pre-approved, non-critical, thoroughly checked, and well-tested changes, originally generated via AI, is permitted. Before submitting a pull request with such changes, the developer must reach an agreement with the reviewers in advance. Proposed changes should be tagged with the label "ai-assisted" and may affect secondary tools such as tidy and linkchecker, but must not concern core capabilities and elements of the language. To track the results of the experiment, changes must be submitted to a separate private Zulip channel, access to which is granted only to project participants.
Source: opennet.ru
