作者：瓦斯的2010_217 | 来源：互联网 | 2023-08-11 17:55
123456789101112131415161718192021#include #include #include #include using namespace std;#define USE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
| #include
#include
#include
#include |
Using eastl::vector_multimap, I get the following error when compiled with: /usr/bin/clang++ -std=c++14 deleteme.cpp -I/usr/local/include on os x sierra
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
| /usr/local/include/EASTL/vector_multimap.h:779:36: error: call to &＃039;equal&＃039; is ambiguous
return (a.size() &＃061;&＃061; b.size()) && equal(b.begin(), b.end(), a.begin());
^~~~~
deleteme.cpp:20:11: note: in instantiation of function template specialization &＃039;eastl::operator&＃061;&＃061;<:__1::basic_string>, int,
eastl::less<:__1::basic_string> >, eastl::allocator, eastl::vector<:pair>, int>,
eastl::allocator> >&＃039; requested here
(void)(a&＃061;&＃061;a);
^
/usr/local/include/EASTL/algorithm.h:1936:2: note: candidate function [with InputIterator1 &＃061; const
eastl::pair<:__1::basic_string>, int> *, InputIterator2 &＃061; const eastl::pair<:__1::basic_string>, int> *]
equal(InputIterator1 first1, InputIterator1 last1, InputIterator2 first2)
^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c&＃043;&＃043;/v1/algorithm:1201:1: note:
candidate function [with _InputIterator1 &＃061; const eastl::pair<:__1::basic_string>, int> *, _InputIterator2 &＃061; const
eastl::pair<:__1::basic_string>, int> *]
equal(_InputIterator1 __first1, _InputIterator1 __last1, _InputIterator2 __first2)
|
该提问来源于开源项目：electronicarts/EASTL
I'd prefer to not break existing code unless there is a compelling reason. std interop isn't a heavily used feature (and is something that I'm looking at deprecating in the future) so even the smallest possibility of breaking users existing code in favor of a feature we don't use doesn't make sense in my mind.
京公网安备 11010802041100号