[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by ad
|
From: |
jonas . hahnfeld |
|
Subject: |
Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden) |
|
Date: |
Tue, 14 Apr 2020 00:00:55 -0700 |
On 2020/04/13 21:01:11, hanwenn wrote:
> it's hard to say if this makes a measurable difference:
>
> [...]
So then ... why do it at all? From a code perspective, a deep copy looks
saner in terms of "encapsulation" (one principle of object-oriented
programming). If there is no provable gain, I'm for leaving the current
code alone until there is good reason to change - "premature
optimization is the root of all evil"
https://codereview.appspot.com/561640045/
- Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), jonas . hahnfeld, 2020/04/13
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), hanwenn, 2020/04/13
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), hanwenn, 2020/04/13
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden),
jonas . hahnfeld <=
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), hanwenn, 2020/04/14
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), jonas . hahnfeld, 2020/04/14
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), jonas . hahnfeld, 2020/04/14
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), hanwenn, 2020/04/14
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), jonas . hahnfeld, 2020/04/14
- Re: Copy alist instead of deep copy on Grob clone (issue 561640045 by address@hidden), hanwenn, 2020/04/15