search for: n1984

...`auto`, range-for, and > `nullptr`, along with library offerings like unique_ptr<>. Just based > on that, the churn and overhead of imposing new build requirements > doesn't seem worth it at the moment. > > -- Sean Silva > Actually, MSVC 10 supports auto as proposed in n1984, which did not yet removed "auto" as a storage specifier. This is not too surprising since auto and decltype go hand in hand functionality wise and I am sorry I missed it. Therefore, given the list above, the gcc 4.5, MSVC 10 combination provides both "auto/decltype" and suffic...

On Sun, Jan 13, 2013 at 2:10 PM, Matthieu Monrocq <matthieu.monrocq at gmail.com> wrote: > gcc 4.5, MSVC 10, clang 3.1 > - decltype v1.0 [1] + late specified return type > - lambda v1.0 [2] > - local types as template arguments > - r-value 2.0 [3] > - static_assert > - built-in type traits This isn't very encouraging. Anecdotally from what I've seen in LLD

...`nullptr`, along with library offerings like unique_ptr<>. Just based >> on that, the churn and overhead of imposing new build requirements >> doesn't seem worth it at the moment. >> >> -- Sean Silva >> > > Actually, MSVC 10 supports auto as proposed in n1984, which did not yet > removed "auto" as a storage specifier. This is not too surprising since > auto and decltype go hand in hand functionality wise and I am sorry I > missed it. > > Therefore, given the list above, the gcc 4.5, MSVC 10 combination provides > both "a...