Bastion 0.3.0 Rollup #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…or it and the supervisors
# Conflicts: # benches/bench_one_for_one.rs # examples/root_spv.rs # examples/spawn_from_context.rs # src/child.rs # src/context.rs # src/lib.rs # src/macros.rs # src/supervisor.rs # tests/lib.rs # tests/test_prelude.rs
# Conflicts: # Cargo.toml # bastion/src/registry.rs # bastion/src/system.rs
…side a BastionID struct
…eceivers after restarting and updated BastionId to generate its own ID by itself
…hild to store received message in it and Context to allow to get messages from it
- Added a really simple example to show how sending and receiving messages works from inside a child (this is a pre-release example, don't worry ;)) - Added support for spawning children from Bastion - Updated System to automatically create a Supervisor with a NIL UUID (set to 0) to supervise those root-level Children - Removed the "launch" method from Supervisor to use a "configuring closure" instead (the closure has the supervisor both as an input and output) - Removed the "msg" argument from the "children" methods and closures - Added support for spawning, stopping and killing remote children - Added support for stopping and killing remote supervisors - Updated System to only start after being asked to - Updated System, Supervisor, Children and Child to register and initialize themselves when created - Prepared Supervisor to have its own sub-supervisors --- Side note: I apparently forgot to add my patch for "qutex" in my previous commit. Please excuse me for that :)
…visor" methods, allowing to configure the now public "Children" using its "with_exec" and "with_redundancy" methods.
…exec and with_redundancy methods and hide Sender and its methods' documentation.
Executor work
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the rollup PR for Bastion's 0.3.0 iteration.
With this merge, Bastion will have:
bastion– New surface API design (continuing our dynamic dispatch approach with more concrete design)bastion-executor– NUMA-aware(optionally) cache affine fault-tolerant executorlightproc– A lightweight process implementation that contains lifecycle callbacks, panic detection with containment and shared stack between processes.