-
Notifications
You must be signed in to change notification settings - Fork 38
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
Does library designed only for working with objects in memory? #25
Comments
It wasn't an explicit design goal, but I guess it indeed only works with objects in memory. However, files (even the big ones) in any case should eventually be loaded into memory to work with them. What exactly are you suggesting should be done instead? |
Read only part of data that you needs at current moment I say about something like this: |
OK, I see. I think, there are two questions being asked:
I considered the second issue at various points in time, and I think it can be resolved, for example, by providing APIs that take Foundation's So, to summarize, I guess there are some plans to try to do something along the lines of what you want, but I can't say when it will happen. |
In All your tests you work with objects in memory
What about big files as example 6 or 7 gb?
The text was updated successfully, but these errors were encountered: