-
Notifications
You must be signed in to change notification settings - Fork 67
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
Persistent history #23
Conversation
Cool. This sure will come in handy during development, when the repl is constantly restarting. I'm curious what your plans are with this. What is sqlite adding to the equation? Why not simply read a file into memory and then search in memory? |
Good question! The design goal I have is to get to feature completeness as soon as possible with reasonable trade-offs. The most difficult part with keeping history is synchronizing writes of multiple processes (when you have multiple shells running) into one file. You have to do low-level file locking, which may behave slightly differently across different platforms. Sqlite does its own robust file locking which makes it easy for us. |
51ca18d
to
8a1308c
Compare
Work in Progress
Tasks: