comex a6f6695ecd Work around MSVC bug, and make it less likely to happen again. Ew.
MSVC insisted on using a copy assignment where a move was intended and
ought to be used.  This would have been caught, because the class in
question inherits from NonCopyable, which declares a move assignment
operator, which is supposed to delete the implicitly declared copy
assignment operator, but of course MSVC didn't do that either, causing a
class that should have been safe to be unsafe.
2013-09-01 00:04:50 -04:00
..
2013-08-28 01:07:43 +12:00
2013-04-24 00:48:00 +12:00
2013-08-15 20:47:47 +12:00
2013-08-28 00:57:08 +12:00
2013-08-28 00:57:08 +12:00
2013-08-29 16:30:32 -04:00
2013-04-21 12:29:18 +02:00