Hi,

Does anyone know the status of

   using auto = <type>;
   <type> operator auto();

? We're currently discussion what to do with our (Qt) expression templates and
were wondering how C++ upstream now plans to handle the issue.

Thanks,
Marc

--
Marc Mutz <marc.mutz@kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt Experts

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/201603221203.03463.marc.mutz%40kdab.com.

.

On 22 March 2016 at 13:03, Marc Mutz <marc.mutz@kdab.com> wrote:
> Hi,
>
> Does anyone know the status of
>
>    using auto = <type>;
>    <type> operator auto();
>
> ? We're currently discussion what to do with our (Qt) expression templates and
> were wondering how C++ upstream now plans to handle the issue.


I don't recall any updates since Rapperswil, so the issue is up to date:
https://cplusplus.github.io/EWG/ewg-active.html#76

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAFk2RUZGk%3DS9a1ftVaB91iiVmjPPYi615NxO%2BZOHczbO9JSE8Q%40mail.gmail.com.

.