docs: updates third-party library guidelines to mention Rust
Change-Id: Iab9176ae605121c05cc8b91136ad34fd011fd657
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4064142
Commit-Queue: danakj <[email protected]>
Reviewed-by: danakj <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1077030}
diff --git a/docs/adding_to_third_party.md b/docs/adding_to_third_party.md
index 1a75cea8..ab88e05 100644
--- a/docs/adding_to_third_party.md
+++ b/docs/adding_to_third_party.md
@@ -35,6 +35,28 @@
existing topics in g/chrome-eng-review, and can also come to office hours to ask
questions.
+### Rust
+
+Rust is allowed for third-party libraries as long as there is a business need,
+which includes the following:
+
+* The Rust implementation is the best (e.g., speed, memory, lack of bugs) or
+only existing implementation available for the third-party library.
+* The Rust implementation allows the operation to move to a higher privileged
+process, and this benefits the product by improving on guardrail metrics (e.g.
+through avoiding process startup, IPC overheads, or C++ memory-unsafety
+mitigations).
+* The Rust implementation can meaningfully reduce our expected risk of
+(memory/crashes/undefined behavior) bugs, when compared to the existing
+third-party library and related C++ code required to use the library. We realize
+assessing risk is quite complex and very nuanced. If this is the criteria by
+which the third-party library is being added, [email protected] and
[email protected] may ask for more data.
+
+Support for third-party libraries written in Rust is in active development. If
+the library you wish to add is in Rust, reach out to [email protected]
+first.
+
### A note on size constraints
The size of Chromium derived executables can impact overall performance of those binaries as they
