|about 1 month ago||4 months ago|
|GNU General Public License v3.0 or later||GNU General Public License v3.0 or later|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Async feedback from 2 years of usage
2 projects | reddit.com/r/rust | 13 Nov 2021
But the issue you're referring to, building a fault-tolerant web server where you can have granular control over killing background jobs regardless if they're blocked on a syscall, totally requires using this kind of software architecture. See Bastion.
Can one code different kind of multithreading paradigms in Rust (BEAM, Node, Go)?
3 projects | reddit.com/r/rust | 29 Sep 2021
Bastion, a Rust async runtime inspired by the beam distribution and supervision model
Linus Torvalds on Rust support in kernel
I don't really know much about erlang, but I think this may be along the lines of what you are thinking of: https://github.com/bastion-rs/bastion
(I also don't really think the linux kernel people would be interested...)
Lunatic - An Erlang inspired runtime for all programming languages
3 projects | reddit.com/r/rust | 8 Mar 2021
This reminds me of bastion. Looks like it attempts to fulfill the same needs, though I guess Lunatic has native WASM support whereas bastion might require some tweaking to have it work? Haven't worked with bastion, so that part of harder time with WASM is just a wild speculation. On the other hand bastion looks much more mature. Probably /u/vertexclique could give a more informed opinion about the difference between the two ;) I really like what these projects are putting forward.
Bastion – A Highly-Available Distributed Fault-Tolerant Runtime for Rust
1 project | reddit.com/r/patient_hackernews | 1 Mar 20211 project | reddit.com/r/hackernews | 1 Mar 20211 project | news.ycombinator.com | 1 Mar 2021
bastion - Highly-available Distributed Fault-tolerant Runtime
2 projects | reddit.com/r/rust | 1 Mar 2021
Three Things Go Needs More Than Generics
7 projects | news.ycombinator.com | 3 Oct 2021
> Doesnt Rust have implicit panics on indexing out of bounds?
It does yes. A fair number of other constructs can panic as well.
> I wonder if any codebases lint those away.
Clippy has a lint for indexing so probably.
For the general case, it's almost impossible unless you're working on very low-level software (embedded, probably kernel-rust eventually) e.g. `std` assumes allocations can't fail, so any allocation will show up as a panic path.
https://github.com/Technolution/rustig can actually uncover panic paths, but because of the above the results are quite noisy, and while it's possible to uncover bugs thanks to rustig it requires pretty ridiculous amounts of filtering.
Linus Torvalds on Rust support in kernel
This comment is strongly confused.
That's a binary analysis tool. It is only approximate, and does not claim to be an accurate analysis like unsafe-checking and typechecking are:
> All paths leading to panic! from one of those functions (whether actually used or not) will be reported.
It also only works on x86_64 binaries.
Panics are an ugly leftover from the bad old days before Rust had nice monad-like syntax for Result error-handling (the "?" syntax). It's time for panic to sunset.
This comment is strongly missinformed:
1- panicking allocations are here to stay, because in lots of case, it's the most convenient behavior. BUT Rust is adding fallible allocations methods (prefixed with try_) which return a result instead of panicking in allocation failure.
2- panics are catch-able as long as you don't compile your binary with panic=abort setting (and as long as you don't panic in your panic handler itself)
3- panics can only occur in specific places (array indexing, allocations, utf-8 validation, unwrap, etc.) which are by definition known at compile-time, and there's tooling to catch these up .
In practice, a might_panic annotation would add a lot of noise for pretty much everybody, because most of us mortals use panicking function all days and it's not a big deal. Obviously it is critical for Linux, but because it's relevant only to the minority of rust users, it doesn't make sense to include it in rustc itself: it's exactly the kind of situation where external tooling is the good option.
What are some alternatives?
actix - Actor framework for Rust.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
smol - A small and fast async runtime for Rust
lumen - An alternative BEAM implementation, designed for WebAssembly
wactor - Ultra minimal actor API wrapper for lunatic