id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
5483	value_init: Assignment to 'value_initialized', 'initialized' objects doesn't work automatically	Christian Masloch <cm@…>	No-Maintainer	"Objects of the 'initialized<T>' class (and presumably 'value_initialized<T>' too) do not automatically convert to assignment lvalues and do not provide proper assignment operator methods either. Assignments therefore do not automatically work, for example, declaring 'initialized<int> i;' then writing 'i = 1;'.

Tested on Windows XP SP3 with MinGW g++ 4.4.1, as well as the (VS 2008) Visual C++ 9.0 compiler. Both compilers report that no match for operator= can be found in that assignment, and that the method 'initialized<int>& initialized<int>::operator=(initialized<int> const&)' is considered as 'candidate' that would fit with a conversion inbetween (from 'int' to 'initialized<int>'), but it's not being used. Conversion operators such as the one defined as 'initialized<int>::operator int&()' apparently do not automatically qualify for lvalues either.

Workarounds specify the necessary conversion or operator method, for example, 'i.operator int&() = 1;' and 'get(i) = 1;' both work.

The attached file contains some tests as well as a class implementing a simplified version of the interface of 'initialized<T>' with a fix. The file also contains the error message from g++. I omitted the one from Visual C++ (because I would have to translate it into English) but it essentially says the same."	Feature Requests	new	To Be Determined	utility	Boost 1.46.1	Problem