Test that using a table that was moved-to from a moved-from table fai…

…ls in sanitizer mode.

We previously added (and then rolled back) validation that caused moving a moved-from table to fail, but since we already validate the use-after-moved-to-from-moved-from case, it seems unnecessary to validate that we never move a moved-from table. Therefore, I don't think we need to pursue rolling forward the validation on moving a moved-from table.

PiperOrigin-RevId: 710749538
Change-Id: I64bbf7fd22fa160b47ad94fb8d51186e2a5bad3c

absl/container/internal/raw_hash_set_test.cc

@@ -3724,6 +3724,16 @@ TEST(Table, MovedFromCallsFail) {
     EXPECT_DEATH_IF_SUPPORTED(t1.contains(1), "moved-from");
     t1.clear();  // Clearing a moved-from table is allowed.
   }
+  {
+    // Test that using a table (t3) that was moved-to from a moved-from table
+    // (t1) fails.
+    ABSL_ATTRIBUTE_UNUSED IntTable t1, t2, t3;
+    t1.insert(1);
+    t2 = std::move(t1);
+    // NOLINTNEXTLINE(bugprone-use-after-move)
+    t3 = std::move(t1);
+    EXPECT_DEATH_IF_SUPPORTED(t3.contains(1), "moved-from");
+  }
 }
 
 }  // namespace