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

*MappedBigList should implement a FlyweightPrototype interface #277

Open
seirl opened this issue Aug 4, 2022 · 1 comment
Open

*MappedBigList should implement a FlyweightPrototype interface #277

seirl opened this issue Aug 4, 2022 · 1 comment

Comments

@seirl
Copy link

seirl commented Aug 4, 2022

Currently there is no way to check dynamically if an BigList implements copy() or not. If all the MappedBigList implemented FlyweightPrototype, it would be easier to make a function that makes a threadsafe copy of any type of BigList.

Unfortunately FlyweightPrototype is in dsiutils, not fastutil, so I don't know what's the best way to proceed here.

@vigna
Copy link
Owner

vigna commented Sep 27, 2022

Well, it's a one-time thing, so one not using reflection? I realize the copy() might not be lightweight. But which other cases would you need to cover (except Mapped vs. non-Mapped)?

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

2 participants