rustyscreeps/oxydized_screeps

Screeps OS written in Rust. Very much in alpha.

oxydized_screeps's Issues

Add threads to the OS.

For the sake of our OS, we would have processes and threads.

Processes can be scheduled and have memory that is theirs only.
Threads could be scheduled and share their memory with their parent process. Doing so could enable easier coordination between multiple jobs, at the price of needing to be more careful with the memory ownership (rust should help with that).

There is something to be said about only having threads running (so a process would spawn a "main thread"). This would make everything fairly uniform from the kernel/scheduler point of view, but would add a layer of complexity on the process side.

Yield should also return a state pointer

This is to implement a poor man's version of generator. If Yield returns an integer, run can use that integer to match where to resume in its code.

• Add a u8 state tracker (maybe wrap it in something fancier?
• Modify the scheduler to keep this in run tasks
• Modify the process trait to receive that state value.

Message Handling

Messages aren't yet supported. A way to handle figuring out where to send a message would be for some processes to act as services and register themselves as such to the kernel using a SysCall::register_service.
Messages could be a HashMap<String, i32>. TBD

• Add a SysCall::send_message that sends a message and then either automatically yield or use as a recursive type.
• Add a SysCall::register_service to register that process to the kernel.
• Modify Kernel::terminate to unregister services.