Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why checking Type equals 0 #15

Closed
xhou-wavefin opened this issue Aug 31, 2017 · 6 comments
Closed

Why checking Type equals 0 #15

xhou-wavefin opened this issue Aug 31, 2017 · 6 comments
Assignees
Labels

Comments

@xhou-wavefin
Copy link

https://github.com/taocpp/json/blob/master/include/tao/json/traits.hpp#L33

In traits, line 33, there is a static assert to check if type size equals 0. Why?

@d-frey
Copy link
Member

d-frey commented Aug 31, 2017

Because it should never be necessary to instantiate the base template. As the static_assert error message says, you need to specialize the traits for each type you are using.

Using sizeof(T)==0 is a trick to make the line depend on the template parameter and which always yields false (since no type can have a size of 0), so you get a nice compile-time error message when you instantiate (aka use) the template with a type without specializing it first. If I would just write static_assert( false, "..." );, the error would appear immediately when compiling the template itself. The error must be deferred until it is instantiated, hence the dependency on a template parameter is required.

@d-frey d-frey closed this as completed Aug 31, 2017
@d-frey d-frey self-assigned this Aug 31, 2017
@xhou-wavefin
Copy link
Author

We experienced this issue when trying to use the library with MSVC 2015. Everything seems to work fine, but this assertion is triggered. We definitely can't be using the traits::assign() function though, since surely that would generate a link time error?

@d-frey
Copy link
Member

d-frey commented Aug 31, 2017

If the assert triggers, it means you forgot to specialize the traits function. Look at the error message, what it T? (The compiler will usually tell you)

That is the type you are trying to use, but there is no traits specialization for that type, hence the library doesn't know what to do with it. The static_assert must trigger to notify you of a problem in your code.

If you can post the error message and a small code example/excerpt, I might be able to help further...

@d-frey d-frey reopened this Aug 31, 2017
@xhou-wavefin
Copy link
Author

xhou-wavefin commented Aug 31, 2017

what it T? (The compiler will usually tell you)

The visual studio compiler is not giving us any useful information.

I commented out all the code that uses your lib but only include the header. The compile output is

c:\projects\app\third_party\json\include\tao\json\traits.hpp(32): error C2338: no traits specialization found c:\projects\app\third_party\json\include\tao\json/value.hpp(118): note: see reference to class template instantiation 'tao::json::traits<std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>>,void>' being compiled with [ _Kty=std::string, _Ty=tao::json::basic_value<tao::json::traits> ] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\xtree(1444): note: while compiling class template member function 'std::_Tree_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>> std::_Tree<std::_Tmap_traits<_Kty,_Ty,_Pr,_Alloc,false>>::erase(std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>>,std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>>)' with [ _Kty=std::string, _Ty=tao::json::basic_value<tao::json::traits>, _Pr=std::less<std::string>, _Alloc=std::allocator<std::pair<const std::string,tao::json::basic_value<tao::json::traits>>> ] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\xtree(2168): note: see reference to function template instantiation 'std::_Tree_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>> std::_Tree<std::_Tmap_traits<_Kty,_Ty,_Pr,_Alloc,false>>::erase(std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>>,std::_Tree_const_iterator<std::_Tree_val<std::_Tree_simple_types<std::pair<const _Kty,_Ty>>>>)' being compiled with [ _Kty=std::string, _Ty=tao::json::basic_value<tao::json::traits>, _Pr=std::less<std::string>, _Alloc=std::allocator<std::pair<const std::string,tao::json::basic_value<tao::json::traits>>> ] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\map(73): note: see reference to class template instantiation 'std::_Tree<std::_Tmap_traits<_Kty,_Ty,_Pr,_Alloc,false>>' being compiled with [ _Kty=std::string, _Ty=tao::json::basic_value<tao::json::traits>, _Pr=std::less<std::string>, _Alloc=std::allocator<std::pair<const std::string,tao::json::basic_value<tao::json::traits>>> ] c:\projects\app\third_party\json\include\tao\json/value.hpp(868): note: see reference to class template instantiation 'std::map<std::string,tao::json::basic_value<tao::json::traits>,std::less<_Kty>,std::allocator<std::pair<const _Kty,_Ty>>>' being compiled with [ _Kty=std::string, _Ty=tao::json::basic_value<tao::json::traits> ] c:\projects\app\third_party\json\include\tao\json/from_string.hpp(78): note: see reference to class template instantiation 'tao::json::basic_value<tao::json::traits>' being compiled

I don't feel the error message is accurate :(

@d-frey
Copy link
Member

d-frey commented Aug 31, 2017

Ah, I see. Well, the error message is basically complaining about a missing specialization for

std::map< std::string, tao::json::basic_value< tao::json::traits > >::const_iterator

but that is most likely a problem in our code. As we are not Visual Studio / Windows users ourselves and the library is in an early stage of development, we haven't found the time to make it compatible with Visual Studio. I know, bad news... sorry.

I am about to refactor some more stuff (probably later today), maybe it solves the problem, maybe not. Probably not. :-/ Anyways, I'm afraid there is no real solution currently. After the next refactoring, we would, of course, appreciate help from actual Visual Studio users if they can figure out ways to fix the problems VS is having and send a pull request. I'll close the question for now, general Visual Studio / Windows support will happen anyways when we have enough time and help in the future.

@d-frey d-frey closed this as completed Aug 31, 2017
@xhou-wavefin
Copy link
Author

Sure, thank you very much for all the help. Enjoy coding :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants