From fb0eb5f793150f0f966622ce14236a8b14c5355f Mon Sep 17 00:00:00 2001 From: Hashim Khan Date: Mon, 27 Jul 2026 13:06:59 +0500 Subject: [PATCH 1/2] Fix release_nested_message typo in C++ arenas guide The inefficient-usage example called release_message() but the field is nested_message, matching the set_allocated and unsafe_arena APIs. --- content/reference/cpp/arenas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/reference/cpp/arenas.md b/content/reference/cpp/arenas.md index d3392759..c367d267 100644 --- a/content/reference/cpp/arenas.md +++ b/content/reference/cpp/arenas.md @@ -474,7 +474,7 @@ The following code makes inefficient usage of the `release_...()` API: ```cpp arena_message_2->set_allocated_nested_message(arena_message_1->release_nested_message()); -arena_message_1->release_message(); // returns a copy of the underlying nested_message and deletes underlying pointer +arena_message_1->release_nested_message(); // returns a copy of the underlying nested_message and deletes underlying pointer ``` Using the "unsafe arena" version instead avoids the copy: From cc5d87bf559c97d32df63999898ed7dd5565052a Mon Sep 17 00:00:00 2001 From: Hashim Khan Date: Tue, 28 Jul 2026 21:59:41 +0500 Subject: [PATCH 2/2] chore: retrigger CLA check after Google CLA username update