FS#1512 Replace type traits by their standard versions
- Jan 19, 2016
-
-
Felix Gruber authored
I still don't understand why, but GCC was spilling deprecation warnings for Dune::enable_if even if we were only using std::enable_if. Thus I removed the deprecation of the enable_if struct and only deprecate the type within. That should still be enough as this deprecation warning gets triggered when enable_if is used to aid in overload resolution and the boolean parameter of enable_if is true.
-
Felix Gruber authored
My previous wrapper implementation around std::enable_if didn't work when B was false, as type was then defined to a type that was SFINAEd away.
-
- Jan 15, 2016
-
-
Felix Gruber authored
Using inheritance for the deprecated wrapper class unfortunately only worked on GCC, so we had to define the type or value of the type trait explicitly to deprecate it.
-
- Jan 12, 2016
-
-
Felix Gruber authored
Since we cannot deprecate using statements, I changed all using statements for std type traits into thin wrapper classes that I then deprecated.
-
- Dec 21, 2015
-
-
Felix Gruber authored
This is not needed anymore, as the testet type traits are directly imported from std:: and can thus be assumed to be correct.
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
Is ConstVolatileTraits still used anywhere? I would propose to deprecate it and replace it with std::is_volatile, std::is_const, std::remove_cv, etc.
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
-
Felix Gruber authored
They can be replaced by std::is_base_of, std::is_const and std::is_volatile, respectively.
-
Felix Gruber authored
-
Felix Gruber authored
Now that we require a C++11-compliant compiler, we can use the std type traits to construct our own.
-
Felix Gruber authored
-
Felix Gruber authored
-