The reason for using C++14 is auto detection of return value in unit tests.<br>
I could create a global FFN and use it to 'decltype'<br>
<br>
On Fri, Feb 12, 2016 at 5:12 AM, Marcus Edel <notifications@github.com><br>
wrote:<br>
<br>
> Okay, great so, I think we should merge this code first and then head over<br>
> to #516 <https://github.com/mlpack/mlpack/pull/516>. We have to slightly<br>
> modify #516 <https://github.com/mlpack/mlpack/pull/516>, I can do that if<br>
> no one likes.<br>
><br>
> About c++14 feature, could we postpone the use of them? Because there are<br>
> a lot of c++14 features do not support by vc2013. Although vc2015 out, but<br>
> cuda do not support vc2015 yet.<br>
><br>
> The test should build using a C++11 compiler because of the<br>
> conditional-compilation directives Joseph used. But I agree, we should<br>
> avoid C++14 features for the moment, we can easily rewrite the test. I can<br>
> do that once the code is merged.<br>
><br>
> —<br>
> Reply to this email directly or view it on GitHub<br>
> <https://github.com/mlpack/mlpack/pull/519#issuecomment-182984919>.<br>
><br>
<br>
<br>
<br>
-- <br>
Joseph Chakravarti Mariadassou<br>
http://thesundayprogrammer.com<br>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/mlpack/mlpack/pull/519#issuecomment-183054592">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AJ4bFP_VLBvI4CsrlaG3gS_hj5IG8jhkks5pjOrEgaJpZM4HWwxL.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/pull/519#issuecomment-183054592"></link>
<meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>