https://svn.boost.org/trac10/ticket/10889 <p> I'm not sure this is the right place to report the issue, but here goes: </p> <p> When I tried to compile the HPX library with the new msvc14 (visual studio 2015 preview), I got several errors which seem to indicate that there are possibly some issues in the std::atomic implementation and some unfortunate interactions with boost::range </p> <p> The errors are attached both as a screenshot and a text file with the compiler output </p> <p> (I'm also reporting this to the msvc and HPX bug trackers) </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10889 Trac 1.4.3 Gijsbert dos Santos <mail@…> Sun, 21 Dec 2014 20:29:53 GMT https://svn.boost.org/trac10/ticket/10889 https://svn.boost.org/trac10/ticket/10889 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">hpx_output.zip</span> </li> </ul> <p> zipped screenshot and compiler output </p> Ticket Neil Groves Sat, 31 Jan 2015 15:06:17 GMT https://svn.boost.org/trac10/ticket/10889#comment:1 https://svn.boost.org/trac10/ticket/10889#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> The compiler log looks like there are problems with symbols being brought into the global namespace. I personally use std::atomic with boost::range admittedly not with MSVC without issue. This would be a very common combination and there are no other reported tickets. </p> <p> I suspect the issue is in code that is bringing symbols into the global namespace with using namespace, or using. std::atomic share no symbols and has absolutely no interaction with Boost.Range. You have a large number of errors reported from template instantiating a large number of Boost libraries. </p> Ticket