-
Notifications
You must be signed in to change notification settings - Fork 199
Dropping implementation of ArrayStorage #294
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
Comments
@Nucs Could you push |
My 2 cents:
Why the hell not ;) This is a huge change though. Can you pull it off? |
@henon, Already did (thanks to regen), looking for approval. |
Just push to your repo. Github will put all commits in one PR automatically. |
Awesome @Nucs, I am looking forward to the PR. |
@Nucs Thank you for your nice comparison, actually, We're using the I refactored it in Our long term goal is implement another |
Was dropped and successfully replaced with |
Uh oh!
There was an error while loading. Please reload this page.
After a deep look at the backend architecture and doing some experiments, I would like you to consider the following benchmark:
Proposition
I propose to drop-off non-generic
ArrayStorage
and only useTypedGenericStorage
.I have already done it in my local but I can't remove base classes without other architects's review.
The text was updated successfully, but these errors were encountered: