moor
moor copied to clipboard
rdaum
A rewrite of the classic LambdaMOO server; but in Rust and on a modern tech stack
https://github.com/rdaum/moor/blob/47435a1442a1f5532c23944029e90982baa99bff/crates/compiler/src/program.rs#L101 ```rust writeln!(f, "V{}: {}", i, v)?; } // TODO: print fork vectors // Display main vector (program); opcodes are indexed by their offset for (i, op) in self.main_vector.iter().enumerate() {...
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
https://github.com/rdaum/moor/blob/47435a1442a1f5532c23944029e90982baa99bff/crates/compiler/src/program.rs#L42 ```rust pub fork_vectors: Vec, /// As each statement is pushed, the line number is recorded, along with its offset in the main /// vector. /// TODO: fork vector offsets......
The tasks in the scheduler are currently not persisted. Problem because: * Restarts of the `daemon` for upgrades, etc. will kill background tasks without recovery on restart, interrupting the user...
I would like a suite of tests to check for correctness of concurrent behaviour; linearizability, consistency, serialization conflicts, etc. Still very vague in my mind, but probably a suite of...
It would be nice to try providing an alternative to the `rocksdb` db implementation that is based around a relational database. When I first started, I used SQLite for this...
Now that I've pretty much de-cloaked on this project and there's some external people watching, it's probably best to document the decisions, vision, and architecture a bit. Basically a couple...
Similar to #21 , I would like to see how this would perform and work out in code. I played with this in an earlier sketch of things, but didn't...
Hi, I'm Volund of the MUSH Community. Been looking into MOO on and off and I found this thanks to reddit... well, really I found it thanks to ToastStunt community...
