From 53d587ee0390301d92ea289bdac557570f9a2973 Mon Sep 17 00:00:00 2001 From: Rui Ueyama Date: Thu, 27 Apr 2017 03:45:33 +0000 Subject: [PATCH] Make StringSaver::save less ambiguous. Previously, an expression such as Saver.save(std::string("foo") + "bar") didn't compile because there is an ambiguity as to whether the argument is of const Twine& or StringRef. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@301512 91177308-0d34-0410-b5e6-96231b3b80d8 --- include/llvm/Support/StringSaver.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/llvm/Support/StringSaver.h b/include/llvm/Support/StringSaver.h index fcddd4cde5b..e85b2895ce5 100644 --- a/include/llvm/Support/StringSaver.h +++ b/include/llvm/Support/StringSaver.h @@ -26,7 +26,7 @@ public: StringRef save(const char *S) { return save(StringRef(S)); } StringRef save(StringRef S); StringRef save(const Twine &S) { return save(StringRef(S.str())); } - StringRef save(std::string &S) { return save(StringRef(S)); } + StringRef save(const std::string &S) { return save(StringRef(S)); } }; } #endif -- 2.40.0