From f9befd31fff811c76594d780bb2f23d709d23f8c Mon Sep 17 00:00:00 2001
From: Jim Blandy <jimb@red-bean.com>
Date: Tue, 17 Oct 2023 23:18:48 +0000
Subject: [PATCH] Bug 1859623: Mention thin-vec crate in Writing Rust Code /
 Basics. r=firefox-source-docs-reviewers,sylvestre DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D191223
---
 docs/writing-rust-code/basics.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/writing-rust-code/basics.md b/docs/writing-rust-code/basics.md
index d91288133b0a..651f24f8b9b7 100644
--- a/docs/writing-rust-code/basics.md
+++ b/docs/writing-rust-code/basics.md
@@ -49,6 +49,8 @@ reflects `nsresult` codes into Rust.
   exposes bindings for XPCOM string types. You can use the same `ns{A,C}String`
   types as C++ for owned strings and pass them back and forth over the
   boundary. There is also `ns{A,C}Str` for dependent or borrowed strings.
+- [thin-vec](https://docs.rs/thin-vec/latest/thin_vec/) provides a
+  Rust `Vec`-like type that is layout-compatible with Gecko's `nsTArray`.
 - [xpcom](https://searchfox.org/mozilla-central/source/xpcom/rust/xpcom/src)
   provides multiple building blocks for a component's implementation.
   - The `RefPtr` type is for managing reference-counted pointers.