Theo M. Bulut
Theo M. Bulut
We need context become / unbecome pattern for solving different message handling states. https://doc.akka.io/docs/akka/current/actors.html#become-unbecome
Currently, we are disabling `-Zmiri-ignore-leaks` prior to https://github.com/rust-lang/miri/issues/1318 . When AtomicPtr is transparent to MIRI enable this back again. Transactional Memory PR will disable checks => https://github.com/bastion-rs/bastion/pull/207
Make everything ready for WASM runtime. The executor should have single thread. This is requested by various people to incorporate Bastion to their projects.
Replace concrete Bastion Executor with Agnostik. So everyone can use whatever they want as guarantee.
**First;** Feel free to edit or comment on this issue (like every other issue of this project). We are getting close one step at a time to building a completely...
Parallel job API will three-dimensional parallelism where dimensions are: 1 - processes 2 - threads 3 - our children (aka actors/agents and their hierarchy) This will enable parallelization off the...
**Is your feature request related to a problem? Please describe.** API for parallel process locals should run be separatable **Describe the solution you'd like** Having a parallel process locals that...
Stale copy from [`rkallos`'s comment on lobste.rs](https://lobste.rs/s/mhky0b/announcing_bastion_0_3_highly_available#c_3wzabf): > > This looks pretty cool! I definitely see the resemblance to Erlang’s model of lightweight processes. That said, I couldn’t find the...
We can separate `bastion` and bastion-executor and create a layer for multiple executors. Further development can go without friction between executor layer and the surface API.
Move all `bastion*` to no_std environment. I have testing devices. I can send out to you if you are in Europe.