Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Troublesome deep-copy on object instantiation #35

Open
airstruck opened this issue Aug 1, 2017 · 0 comments
Open

Troublesome deep-copy on object instantiation #35

airstruck opened this issue Aug 1, 2017 · 0 comments

Comments

@airstruck
Copy link

airstruck commented Aug 1, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant