rvalues -> ref (yup... again!)
Manu
turkeyman at gmail.com
Sat Mar 24 04:04:15 UTC 2018
On 23 March 2018 at 20:19, Timon Gehr via Digitalmars-d
<digitalmars-d at puremagic.com> wrote:
> On 24.03.2018 04:14, Manu wrote:
>>
>> On 23 March 2018 at 20:03, Timon Gehr via Digitalmars-d
>> <digitalmars-d at puremagic.com> wrote:
>>>
>>> On 24.03.2018 01:35, Manu wrote:
>>>>
>>>>
>>>> Okay, let's read 'const ref' every time I say 'ref'. I thought that
>>>> would be fairly safe to assume. Sorry!
>>>
>>>
>>>
>>> Absolutely not. It makes absolutely no sense to restrict rvalue
>>> references
>>> to const objects. (Recall that const is transitive and actually prevents
>>> mutation. This is not C++.)
>>
>>
>> We're not talking about rvalue-references... were talking about
>> not-rvalue-references to temporaries.
>>
>
> Let me rephrase:
>
> Absolutely not. It makes absolutely no sense to force const for
> not-rvalue-references to temporaries. (Recall that const is transitive and
> actually prevents mutation. This is not C++.)
Yes, I know... why would you mutate an argument who's life doesn't
extend beyond the call? Any mutation is pointless.
More information about the Digitalmars-d
mailing list