updated docs

docs/docs/other.xml

@@ -978,7 +978,7 @@
          <description>
             This is actually a set of overloaded functions which provide the ability to restore an object's state
             from an input stream.  Currently all dlib container classes, non pointer C++ intrinsics, std::string, 
-            std::vector, std::map, std::complex, dlib::bigint, dlib::uint64, dlib::int64, C style arrays, and dlib::vector objects are serializable.  
+            std::vector, std::map, std::set, std::complex, dlib::bigint, dlib::uint64, dlib::int64, C style arrays, and dlib::vector objects are serializable.  
             <p>
                You can also use serialize() and deserialize() to read/write Google protocol buffer objects.  However, 
                note that dlib::serialize() writes additional delimiting bytes at the start of each protocol buffer message.  
@@ -1002,7 +1002,7 @@
          <description>
             This is actually a set of overloaded functions which provide the ability to save an object's state
             to an output stream.  Currently all dlib container classes, non pointer C++ intrinsics, std::string, 
-            std::vector, std::map, std::complex, dlib::bigint, dlib::uint64, dlib::int64, C style arrays, and dlib::vector objects are serializable.   
+            std::vector, std::map, std::set, std::complex, dlib::bigint, dlib::uint64, dlib::int64, C style arrays, and dlib::vector objects are serializable.   
             <p>
                You can also use serialize() and deserialize() to read/write Google protocol buffer objects.  However, 
                note that dlib::serialize() writes additional delimiting bytes at the start of each protocol buffer message.