On Sunday, 15 December 2013 at 23:38:57 UTC, comco wrote:
On Sunday, 15 December 2013 at 23:13:39 UTC, Jakob Ovrum wrote:
On Friday, 13 December 2013 at 12:01:28 UTC, comco wrote:
From client perspective, properties look like member
variables.
With (auto) ref, a generic function can catch a mem
On Sunday, 15 December 2013 at 23:13:39 UTC, Jakob Ovrum wrote:
On Friday, 13 December 2013 at 12:01:28 UTC, comco wrote:
From client perspective, properties look like member variables.
With (auto) ref, a generic function can catch a member
variable and read it and update it:
void swap(T)(ref
On Friday, 13 December 2013 at 12:01:28 UTC, comco wrote:
From client perspective, properties look like member variables.
With (auto) ref, a generic function can catch a member variable
and read it and update it:
void swap(T)(ref T a, ref T b) {...}
The client can use swap with member variabl
On Friday, 13 December 2013 at 12:01:28 UTC, comco wrote:
From client perspective, properties look like member variables.
With (auto) ref, a generic function can catch a member variable
and read it and update it:
void swap(T)(ref T a, ref T b) {...}
The client can use swap with member variabl
From client perspective, properties look like member variables.
With (auto) ref, a generic function can catch a member variable
and read it and update it:
void swap(T)(ref T a, ref T b) {...}
The client can use swap with member variables.
But he can't use this swap with class properties - they
