<p>Sure, I am glad that it helped.</p>

<p>There are two options for serialization support for STL containers that hold mlpack objects: the first is to simply reimplement the STL container serialization support inside the class that uses the container (but that is a little ugly).  The second is a bit uglier:</p>

<p>A class template specialization can be added for each <code>SecondShim&lt;std::type&lt;...&gt;&gt;</code> object.  Inside of this  class, the <code>serialize()</code> method can be implemented in such a way that it is just the implementation of the STL container's <code>serialize()</code> function, except with <code>BOOST_SERIALIZATION_NVP()</code> replaced with <code>ar &amp; data::CreateNVP(...)</code>.</p>

<p>It would be kind of complex and would require testing (although the test case would be simple... just make sure that <code>ar &amp; data::CreateNVP(some STL container)</code> compiles).  I personally don't have any plans to implement this right now, but if you would like to the contribution would be welcome. :)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/mlpack/mlpack/issues/811#issuecomment-260788088">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJ4bFCjDv2fFvH0khP__Hwb8Zl_-tCVOks5q-i-LgaJpZM4Kwpgr">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AJ4bFGiyLHSay93-_GG5NXSTCy_7wViyks5q-i-LgaJpZM4Kwpgr.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/mlpack/mlpack/issues/811#issuecomment-260788088"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/mlpack/mlpack","title":"mlpack/mlpack","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/mlpack/mlpack"}},"updates":{"snippets":[{"icon":"PERSON","message":"@rcurtin in #811: Sure, I am glad that it helped.\r\n\r\nThere are two options for serialization support for STL containers that hold mlpack objects: the first is to simply reimplement the STL container serialization support inside the class that uses the container (but that is a little ugly).  The second is a bit uglier:\r\n\r\nA class template specialization can be added for each `SecondShim\u003cstd::type\u003c...\u003e\u003e` object.  Inside of this  class, the `serialize()` method can be implemented in such a way that it is just the implementation of the STL container's `serialize()` function, except with `BOOST_SERIALIZATION_NVP()` replaced with `ar \u0026 data::CreateNVP(...)`.\r\n\r\nIt would be kind of complex and would require testing (although the test case would be simple... just make sure that `ar \u0026 data::CreateNVP(some STL container)` compiles).  I personally don't have any plans to implement this right now, but if you would like to the contribution would be welcome. :)"}],"action":{"name":"View Issue","url":"https://github.com/mlpack/mlpack/issues/811#issuecomment-260788088"}}}</script>