SaaSHub helps you find the best software and product alternatives Learn more →
Rustig Alternatives
Similar projects and alternatives to rustig
-
Rust-for-Linux
Adding support for the Rust language to the Linux kernel. (by Rust-for-Linux)
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
prusti-dev
A static verifier for Rust, based on the Viper verification infrastructure.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
gdbstub
An ergonomic, featureful, and easy-to-integrate implementation of the GDB Remote Serial Protocol in Rust (with no-compromises #![no_std] support)
-
-
-
-
-
-
no-panic
Discontinued Attribute macro to require that the compiler prove a function can't ever panic
-
-
carbon-lang
Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
-
-
-
-
macro_railroad_ext
Display syntax-diagrams for Rust-macros on docs.rs and doc.rust-lang.org
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
rustig reviews and mentions
-
Is there something like "super-safe" rust?
There is also rustig though it seems quite dead.
-
Is Rust really safe? How to identify functions that can potentially cause panic
There’s the rustig tool (https://github.com/Technolution/rustig) that looks for code paths leading to the panic handler. Not sure if it still works though.
-
My thoughts on Rust and C++
That's fair. I think I may just be a bit sore that Rustig was allowed to bit-rot and findpanics hasn't seen a commit since 2020.
- What improvements would you like to see in Rust or what design choices do you wish were reconsidered?
-
Things I hate about Rust, redux
There's Rustig which does it for panics, though it seems unmaintained and uses inspection of the final binary rather than source code/AST inspection.
You might be interested in this: https://github.com/Technolution/rustig
-
Three Things Go Needs More Than Generics
> 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.
> [1] https://github.com/Technolution/rustig
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:
https://github.com/Technolution/rustig#limitations
> 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 [1].
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 29 Mar 2024
Stats
Technolution/rustig is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of rustig is Rust.