<p>Okay, maybe we can avoid such situations in the future by assigning the task to the first person who says, I like to work on the issue.</p>

<p>I take a quick look at the pull requests and maybe we can find a way to include both requests.</p>

<p><code>adam_impl.hpp</code> is basically the same so I like to use that from <a href="https://github.com/vasanthkalingeri" class="user-mention">@vasanthkalingeri</a>, but the test is kind of different, <a href="https://github.com/vasanthkalingeri" class="user-mention">@vasanthkalingeri</a> created a new file instead of updating the old test. So I would use the test from <a href="https://github.com/anamariabs" class="user-mention">@anamariabs</a>, also <a href="https://github.com/anamariabs" class="user-mention">@anamariabs</a> added a CMakeLists.txt file to build the optimizer wich is great, so I would also use that. If you both agree, maybe you can update the pull request in that direction?</p>

<p>Since <a href="https://github.com/sshkhrnwbie" class="user-mention">@sshkhrnwbie</a> was the first who said he would like to work on the issue I assign the issue to him, Adadelta is still open. Sorry <a href="https://github.com/awhitesong" class="user-mention">@awhitesong</a>, but I guess that's the best way to avoid such situations.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href="https://github.com/mlpack/mlpack/issues/555#issuecomment-195423032">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AJ4bFED-ca1yOcpyw69YaIbrpCWaaQ3sks5psY7-gaJpZM4HrSVF.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/555#issuecomment-195423032"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>