Closed marschall closed 2 years ago
Wondering: is this an issue somewhere. In other words: isn't the following true?
nil copy == nil
Wondering: is this an issue somewhere. In other words: isn't the following true?
nil copy == nil
Yes, it's true. It goes through Object >> #copy
which goes through UndefinedObject >> #shallowCopy
which returns self
and then goes through Object >> #postCopy
.
I guess I could file a bug against Pharo as well.
Trying to understand the issue here... You mean UndefinedObject>>copy
should be defined returning nil
?
Trying to understand the issue here...
We send #copy
to nil
. This sometimes shows up during profiling.
You mean UndefinedObject>>copy should be defined returning nil ?
Probably.
In a recent profiling
UndefinedObject(Object)>>copy
showed up, the culprit wasWAUrl >> #postCopy