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

Is there a way to save a Triez to file and load it again? #2

Open
canadaduane opened this issue Mar 21, 2014 · 4 comments
Open

Is there a way to save a Triez to file and load it again? #2

canadaduane opened this issue Mar 21, 2014 · 4 comments

Comments

@canadaduane
Copy link

Nice work with this gem. I've been looking through the source for possible ways to save and load a trie using Triez. I haven't seen anything in the source yet, but I'm curious if you have any thoughts or suggestions?

@luikore
Copy link
Owner

luikore commented Mar 22, 2014

Thank you. I think this feature is very important too!

But the underlying implementation (HAT-trie) can not do this either...

HAT-trie is composed of data buckets, we may save and load these buckets in a shorter time than iterating all key-values. I think it's not hard to achieve the goal (just change the memory allocation functions and serialize chunk pointers), or, maybe some one has already done it (do you have any idea?). Currently I'm working on other stuffs but will come back try to make it next week.

@lilith
Copy link

lilith commented Mar 29, 2014

I ran into this issue too. Marshal.dump/load compatibility would be fantastic, even if at a performance penalty.

@oddg
Copy link

oddg commented Feb 23, 2015

I am also really interested in this feature. Did you find a way?

@canadaduane
Copy link
Author

I started work on it, but did not finish due to a hope that the code bases
would be merged first so that my effort would benefit both this project and
upstream.

On Mon, Feb 23, 2015 at 4:01 PM, oddg [email protected] wrote:

I am also really interested in this feature. Did you find a way?


Reply to this email directly or view it on GitHub
#2 (comment).

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

4 participants