Why is there not an std::is_struct type trait?

by

It returns true for both classes and structs. I know that in C++ they are almost the same thing, but I’d like to know why there’s not a distinction between them in the type trait.

Unfortunately this is a common misconception in C++. Sometimes it comes from fundamental misunderstanding, but at other times it comes from an ambiguity in English. It can come from inaccurate compiler diagnostics, badly-written books, incorrect SO answers…

You’ve probably read something like this:

“There is no difference in C++ between a struct and a class except the default visibility of members and bases.”

This passage can be interpreted in a sense that is misleading, because the notions of identity and equality are hard to distinguish when using phrases like “no difference”.

In fact, C++ has not had structs since 1985. It only has classes.

The kind of types that you declare with the keyword class and the keyword struct are classes. Period. The keyword struct, and the visibility rules that are the default when defining a class using that keyword, were kept only for backward compatibility with C … but that’s a syntax thing. It doesn’t make the resulting types actually be of a different kind.

The type trait makes no distinction because there literally isn’t one to make.

More Related Contents:

  1. check variadic templates parameters for uniqueness
  2. Checking a member exists, possibly in a base class, C++11 version
  3. What do compilers do with compile-time branching?
  4. What is decltype with two arguments?
  5. Is it possible to determine if a type is a scoped enumeration type?
  6. Disambiguate overloaded member function pointer being passed as template parameter
  7. Which cannot be implemented without compiler hooks?
  8. Check traits for all variadic template arguments
  9. False positive with is_copy_constructible on vector
  10. C++11 is_same type trait for templates
  11. “What happened to my SFINAE” redux: conditional template class members?
  12. should std::common_type use std::decay?
  13. C++ press enter to continue
  14. Visual Studio support for new C / C++ standards?
  15. How do I check for C++11 support?
  16. Thread pooling in C++11
  17. Why can’t simple initialize (with braces) 2D std::array? [duplicate]
  18. Why user-defined move-constructor disables the implicit copy-constructor?
  19. How do I properly use std::string on UTF-8 in C++?
  20. How to enable C++11 in CLion?
  21. copy vs std::move for ints
  22. How performing multiple matrix multiplications in CUDA?
  23. What are the main purposes of std::forward and which problems does it solve?
  24. Operator overload which permits capturing with rvalue but not assigning to
  25. Why is auto_ptr being deprecated?
  26. Why was pair range access removed from C++11?
  27. Interfacing C++11 array with Cython
  28. const auto std::initializer_list difference between Clang and GCC
  29. Workaround for error C2536: cannot specify explicit initializer for arrays in Visual Studio 2013
  30. Is it possible to write an agile Pimpl in c++?

Leave a Comment