Idan Arye

Won't this kind of defeat the whole purpose of having an actor system?

@balsa02 What happens if I have something like this: ```rust struct MyActor { data: std::cell::HashMap, } #[async_trait(?Send)] impl AsyncHandler for MyActor { type Result = Result; async fn handle(&mut self,...

> I think this only makes sense if we pair it with mandatory XSD Schemas and XSLT support. XSD? Sure. XSLT? The readme says: > Templates are too complicated, therefore...

Is this new? Could the attention from the EXE thing (which is, BTW, what brought me here. I don't care about stalking people) have generated enough new starts to break...

I can merge the timer commit as soon as you solve the eval problem - and then you can rebase this PR. This is not a problem. What is a...

Vebugger is designed to allow adding features to some debuggers without having to implement them(right away) in all the debuggers: * If you don't implement a read handler, the `readResult`...

Wait what why? Are you completely bypassing Vebugger to send the stack trace to tmux?

The general idea: Saving be triggered by sending a `YoleckInitiateSave` event, which will make Yoleck run a `YoleckSchedule::Save` schedule where save systems will generate `YoleckComponent`s based on the current state...

Each entity type will have to declare its save strategy. I imagine three strategies (names TBD): 1. Unsaved entity types. Example - walls. These will be loaded from the `.yol`...

This looks like a [vimproc](https://github.com/Shougo/vimproc.vim) error. Did you try `make`ing it again?