You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the errors were introduced in issue #476, steemit/fc@19d41b8...a1354c5#diff-18f79c66780a65dbb617edf936a5dd38R115
when more variadic template parameters code was added, the vs2013 compiler is confused about some of the call functions.
The definition of reflector\steem\libraries\fc\include\fc\reflect\reflect.hpp maybe the cause.
Because \steem\libraries\fc\include\fc\reflect\variant.hpp line 104
They both used reflector to determine typename. and both are on the error log. If I commented out the "unpack" template, the "unpack ambiguous call" errors disappear. If I commented out the "from_variant" template, the "ambiguous call" errors are gone, but it generate error LNK2019:unresolved external symbol errors.
The first ambiguous call is from fc/reflect/variant.hpp line 53
template<typename Member, class Class, Member (Class::*member)>
void operator()( const char* name )const
{
auto itr = vo.find(name);
if( itr != vo.end() )
from_variant( itr->value(), val.*member );
}
Here is the logs that is related to from_variant call from the flat_map template.
F:\Git_GUI\steem\libraries\fc\include\fc/container/flat.hpp(118): or
'void fc::from_variant<std::string,steemit::chain::weight_type,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>>(const fc::variant &,boost::container::flat_map<Key,T,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>> &)'
F:\Git_GUI\steem\libraries\fc\include\fc/variant.hpp(94): or
'void fc::from_variant<std::string,steemit::chain::weight_type,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>>(const fc::variant &,boost::container::flat_map<Key,T,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>> &)'
F:\Git_GUI\steem\libraries\fc\include\fc/reflect/variant.hpp(104): or
'void fc::from_variant<boost::container::flat_map<std::string,steemit::chain::weight_type,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>>>(const fc::variant &,boost::container::flat_map<Key,T,std::less<_Kty>,boost::container::new_allocator<std::pair<Key,T>>> &)'
The second ambiguous call is from raw.hpp line 292.
When I compiled v0.14.2 I had no issues after I applied these changes.
But, when I am trying to compile v0.14.3rc1 and v0.15.0. It has the following errors.
" ambiguous call to overloaded function "
https://img1.steemit.com/0x0/http://dirtyimg.com/image/8error.PNG
I believe the errors were introduced in issue #476,
steemit/fc@19d41b8...a1354c5#diff-18f79c66780a65dbb617edf936a5dd38R115
when more variadic template parameters code was added, the vs2013 compiler is confused about some of the call functions.
The definition of
reflector
\steem\libraries\fc\include\fc\reflect\reflect.hpp maybe the cause.Because \steem\libraries\fc\include\fc\reflect\variant.hpp line 104
and \steem\libraries\fc\include\fc\io\raw.hpp line 531
They both used
reflector
to determine typename. and both are on the error log. If I commented out the "unpack" template, the "unpack ambiguous call" errors disappear. If I commented out the "from_variant" template, the "ambiguous call" errors are gone, but it generate error LNK2019:unresolved external symbol errors.from_variant
call from the flat_map template.fc::raw::unpack
call from the flat_map template.I hope someone is able to figure out the actual cause of these errors and correct them.
Thanks for reading.
The text was updated successfully, but these errors were encountered: