Ryan Daum

Sure, I mean, there's other emacs that are written 100% in Lisp. E.g. lem https://github.com/lem-project/lem is 100% Common Lisp, and Zmacs on Lisp Machines (https://en.wikipedia.org/wiki/Zmacs)

I've been using this feature ( through manual commit hash in `Cargo.toml`) as part of a datastructure I've written (e.g. https://github.com/rdaum/rart-rs/blob/main/rart/src/keys/array_key.rs#L25), and wondering what the status on it is? If...

Yes, it requests that memory but only uses what it needs, part of the DB pool logic. The OS properly configured should still give it. It may be that vm.overcommit...

You may need to set `/proc/sys/vm/overcommit_memory` to "1". https://www.baeldung.com/linux/overcommit-modes

For more explication. Moor builds out its own custom database and does not use an off the shelf key value store. In the future I may go back to providing...

Without getting into the weeds of your specific case ... I think the right thing to do is to perform that communication inside the moor runtime itself in Rust code....

Actual syntax is more conservative. ``` begin let a = 5; const b = 3; global c = 2; implicit_global = 1; end ```

Remaining work here is: * ~~add `let` as an option for scatter assignment operations so that scatter-assigns are declared lexically scoped~~ * lexically scoped iteration variables for `for`; something like...

There are some initial tests for Task, but not for the Scheduler loop itself (which would be trickier)

https://github.com/rdaum/moor/pull/323