https://svn.boost.org/trac10/ticket/9396 <p> When 'boost/gil/bit_aligned_pixel_iterator.hpp' is included, the compiler selects for whatever reason an std::uninitialized_copy overload from the gil header instead of boost::cb_detail::uninitialized_copy within boost::cb_detail::uninitialized_move_if_noexcept_impl (boost/circualr_buffer/details.hpp) for types with !boost::is_nothrow_move_constructible. A workaround (solution?) is to fully qualify the call to boost::cb_detail::uninitialized_copy, but why the std overload gets even selected? Is this a compiler bug? Or a gil problem? </p> <p> Tested on: Windows 7 SP1 x64 + MSVC 2010 SP1 </p> <pre class="wiki">#include &lt;boost/circular_buffer.hpp&gt; #include &lt;boost/gil/bit_aligned_pixel_iterator.hpp&gt; // comment this to resolve struct Foo { Foo(const Foo&amp;) {} }; int main(int, char*[]) { #if 1 boost::circular_buffer&lt;Foo&gt; buffer; buffer.set_capacity(42); #endif #if 0 // minimum example typedef boost::cb_details::iterator&lt; boost::circular_buffer&lt;int&gt; , boost::cb_details::nonconst_traits&lt; std::allocator&lt;int&gt; &gt; &gt; InputIterator; boost::cb_details::uninitialized_move_if_noexcept_impl&lt;int&gt;(InputIterator(), InputIterator(), (int*)nullptr, boost::false_type()); #endif return 0; } </pre> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9396 Trac 1.4.3