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

Freeze objects that really do need to keep their values the same #991

Open
knod opened this issue Nov 11, 2018 · 1 comment
Open

Freeze objects that really do need to keep their values the same #991

knod opened this issue Nov 11, 2018 · 1 comment

Comments

@knod
Copy link
Collaborator

knod commented Nov 11, 2018

Like data from programs, non-clone clients, etc.

@knod knod added this to To do in 2:2 Refactoring: Other via automation Nov 11, 2018
@knod knod added this to To do in 3:4 Maintainability via automation Nov 11, 2018
@turnerhayes
Copy link
Collaborator

There is an implementation of a deepFreeze function that has since been deleted from the codebase since it's not being used anymore, but it's still visible here if whoever takes this on wants to use or adapt it. That function returns a frozen clone of the object passed in, rather than freezing the object in-place; that may or may not be desirable here. If we want an in-place freezer, there's a library that does that (have not tested it myself though).

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

No branches or pull requests

2 participants