Described in detail here, along with an explanation of how it affects that particular project.
Specifically, this is a feature request for either entirely scrapping deep-copy on instantiation, or allowing 30log to be configured in such a way that it doesn't happen. Deep-copy on inheritance isn't an issue (or rather, it's a separate issue that doesn't happen to affect us right now; see #29).
It looks like we'll be scrapping 30log for now because of this, but the library in question is designed to allow arbitrary class modules to be plugged in by the user. Ideally the user would be able to plug 30log back in without adversely affecting performance and breaking automated tests.
Described in detail here, along with an explanation of how it affects that particular project.
Specifically, this is a feature request for either entirely scrapping deep-copy on instantiation, or allowing 30log to be configured in such a way that it doesn't happen. Deep-copy on inheritance isn't an issue (or rather, it's a separate issue that doesn't happen to affect us right now; see #29).
It looks like we'll be scrapping 30log for now because of this, but the library in question is designed to allow arbitrary class modules to be plugged in by the user. Ideally the user would be able to plug 30log back in without adversely affecting performance and breaking automated tests.