1. many things antithesis finds in go, kotling, cpp just do not exist in rust. that i less needed case. these people like antithesis.
2. i mentioned tooling, also in other thread i mentioned ecosystem
- https://github.com/BurtonQin/Awesome-Rust-Checker
- add link for dozen of tools for cfg feature(product lines) eng here (compile time conditional composeability) and const expressions
- add link to dozen of tools to audit deps and decide on panic safety and first class crash hooks crates
- mix with nix which many (way many compared to go, kotlin, cpp) rust projects use (and sri cargo.lock out box)
- and qemu/mozilla/no rr tools (no determinism to get seed, and run slower hosts things w that seed)
- and add here clusterfuzz eco (supports all oss fuzzers, and these do proper search https://camshaft.github.io/bolero/features/unified-interface..., and rust adapters allow for manual macro based fuzz narrowing in rust)
- https://quint-lang.org/docs/model-checkers
- several ongoing projects formalizing rust std and lang
SO, why i need antithesis?
To get Raft, will do sans-io with full typed rust covered by proofs for state(machine) and macro generator for glue(from state machine).
I need only prop/fuzz test to test small integration sans-io part. I do not need antithesis.
Literally none of the things you mention help with verifying distributed systems. I think you just fundamentally aren't understanding what it is and this isn't the right forum for me to bridge that gap for you. You highlight this lack of understanding by dismissing a custom hypervisor as a collection of bash scripts and focusing on things Rust has or does well that are completely irrelevant for the classes of bugs that Antithesis is trying to uncover.
> To get Raft, will do sans-io with full typed rust covered by proofs for state(machine) and macro generator for glue(from state machine). I need only prop/fuzz test to test small integration sans-io part. I do not need antithesis.
Again, I think you're missing the point entirely. With hand written property test/fuzz test, you have to manually and correctly implement all the failure conditions that can happen "sans-io". A notable one would be packet reordering (if you're I/O doesn't guarantee ordering) or network partitions. The point of Antithesis is that it will transparently do all of that state checking for you. It's not that you'd not get there eventually, but Antithesis will be an easier system and you'll move faster. Whether or not that's valuable is a decision everyone makes for themselves.