From 93674ec1f0ba3fb4560e4413978e2012816df9f5 Mon Sep 17 00:00:00 2001
From: Joshua Liebow-Feeser <joshlf@users.noreply.github.com>
Date: Thu, 10 Oct 2024 08:18:18 -0700
Subject: [PATCH] Update 2024-10-16-this-week-in-rust.md

---
 draft/2024-10-16-this-week-in-rust.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/draft/2024-10-16-this-week-in-rust.md b/draft/2024-10-16-this-week-in-rust.md
index dfa14bd01..ea92e7c46 100644
--- a/draft/2024-10-16-this-week-in-rust.md
+++ b/draft/2024-10-16-this-week-in-rust.md
@@ -66,6 +66,8 @@ RFCs would benefit from user testing before moving forward:
 <!-- or if there are no new or updated RFCs this week, use: * *No New or Updated RFCs were created this week.* -->
 <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
 
+* Do you use unions and care about how they are represented in memory? The zerocopy authors [want to hear from you](https://github.com/google/zerocopy/discussions/1802)!
+
 If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
 label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
 need testing.