NDDEM
|
Support for types found in <set> More...
Go to the source code of this file.
Namespaces | |
cereal | |
in certain simple scenarios. They should probably not be used if maximizing performance is the main objective. | |
cereal::set_detail | |
Functions | |
template<class Archive , class SetT > | |
void | cereal::set_detail::save (Archive &ar, SetT const &set) |
template<class Archive , class SetT > | |
void | cereal::set_detail::load (Archive &ar, SetT &set) |
template<class Archive , class K , class C , class A > | |
void | cereal::CEREAL_SAVE_FUNCTION_NAME (Archive &ar, std::set< K, C, A > const &set) |
Saving for std::set. More... | |
template<class Archive , class K , class C , class A > | |
void | cereal::CEREAL_LOAD_FUNCTION_NAME (Archive &ar, std::set< K, C, A > &set) |
Loading for std::set. More... | |
template<class Archive , class K , class C , class A > | |
void | cereal::CEREAL_SAVE_FUNCTION_NAME (Archive &ar, std::multiset< K, C, A > const &multiset) |
Saving for std::multiset. More... | |
template<class Archive , class K , class C , class A > | |
void | cereal::CEREAL_LOAD_FUNCTION_NAME (Archive &ar, std::multiset< K, C, A > &multiset) |
Loading for std::multiset. More... | |
Support for types found in <set>