-
Notifications
You must be signed in to change notification settings - Fork 13
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
Disallow mutable eltype in PooledArray #51
Comments
It would indeed be safer. As an alternative maybe we could use an |
Then, given we have tagged PooledArrays.jl as 1.0, maybe we just add a warning not to mutate the stored objects? |
Hmmm, in Arrow.jl, you're allowed to dict-encode anything you want, but then again, everything is assumed immutable, so this isn't really an issue. On the one hand, no one has ever brought this up, so I wonder if people tend to not do this anyway, or just don't run into it. A warning might be fine, just as a way to see if anybody might be doing some mutating unintentionally. But I think we should keep allowing mutable eltypes for now. |
Fixes #51 @nalimilan - as usual - if you have comments on the language or in general how the docstring could be improved please let me know.
I think we should disallow allowing mutable elements of
PooledArray
.The reason of this proposal is the following problem:
Alternatively we should change how
invpool
is handled if mutable objects are stored inPooledArray
or explicitly warn that it is not allowed to mutate them.The text was updated successfully, but these errors were encountered: