|
Boost : |
From: Fernando Cacciola (fernando_cacciola_at_[hidden])
Date: 2005-10-24 15:48:33
Mat Marcus wrote:
> On 10/18/05, Fernando Cacciola <fernando_cacciola_at_[hidden]> wrote:
>>
>> David Abrahams wrote:
>>> Anthony Williams <anthony_w.geo_at_[hidden]> writes:
>>>
>>>> How's this for a radical thought --- optional<T> should not be
>>>> assignable from T. That way, it doesn't matter whether T is a
>>>> reference, or not.
>>>
>>> There's at least some precedent for types that are "immutable except
>>> for copy assignment."
>>>
>>> The assignment from T is really a kind of mutating operation.
>>>
>> Indeed.
>> I'm leaning fast into dropping assignment form T.
>> That definitely solves the reference binding issues.
>
> [snip]
>
> Please review this dicsussion thread from 2003 <
> http://aspn.activestate.com/ASPN/Mail/Message/boost/1788454> before
> discarding assignment from T.
>
I just read it but got sort of lost past the "uniformity with tie" issue.
Can you recap your own issues with dropping direct assignment?
TIA
-- Fernando Cacciola SciSoft http://fcacciola.50webs.com/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk