From dbec2fa2f60e9df86733d050281cccefc30b3b5a Mon Sep 17 00:00:00 2001
From: Corentin Wallez <cwallez@chromium.org>
Date: Mon, 4 May 2020 16:04:40 +0000
Subject: [PATCH] Use unordered_set<std::string> for deprecation warnings

This fixes the roll in Google3, otherwise it complains that
unordered_set<const char*> hashes the pointer, which is most likely not
what you want to do.

Bug: dawn:394
Change-Id: I1ef06c923bb45e55b39c23e5e7734f1577c47255
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/20860
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
---
 src/dawn_native/Device.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/dawn_native/Device.cpp b/src/dawn_native/Device.cpp
index 2fbf2c88fb..90536c7ef4 100644
--- a/src/dawn_native/Device.cpp
+++ b/src/dawn_native/Device.cpp
@@ -74,7 +74,7 @@ namespace dawn_native {
     };
 
     struct DeviceBase::DeprecationWarnings {
-        std::unordered_set<const char*> emitted;
+        std::unordered_set<std::string> emitted;
         size_t count = 0;
     };