------- Comment #3 from redi at gcc dot gnu dot org 2009-11-30 10:38 -------
(In reply to comment #2)
> The issue is pretty simple, actually: std::unique_future (which, by the way,
> will be renamed just std::future), is missing move assignment operator. Note,
> in N2914 it does *not* exist, has been added only in N3000, I guess we can as
> well add it right now, before the rename. But again, consider that these
> facilities are still experimental, the working draft is changing rather
> quickly...
I've already done most of the changes to update <future> to n3000, including
adding move assignment, I just need to adjust the tests because lots of the old
behaviour that was tested has changed (e.g. no default construction)
--
redi at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redi at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42201
