hifitime
prusti-dev
| hifitime | prusti-dev | |
|---|---|---|
| 2 | 23 | |
| 297 | 1,466 | |
| 0.7% | 1.0% | |
| 9.0 | 8.5 | |
| 5 days ago | 11 days ago | |
| Rust | Rust | |
| Apache License 2.0 | 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.
hifitime
-
Is there something like "super-safe" rust?
kani (e.g. used by hifitime)
-
Hifitime 3.5.0: time.rs and chrono alternative, only more precise, formally verified, and used in scientific and engineering programs
I could add that to the documentation. There's a benchmark test here: https://github.com/nyx-space/hifitime/actions/runs/3257976296.
prusti-dev
-
Using_Prolog_as_the_AST
> The overall goal would be to figure out classical error conditions like nill pointers deference.
> If I can figure out if a pointer will be nil in some execution branch, there is no reason why a computer cannot do the same.
Note, this is called flow-sensitive typing (also called type narrowing) and I think that typescript does it.
https://en.wikipedia.org/wiki/Flow-sensitive_typing
> I personally would see this as an human race level upgrades. Imagine feeding your code to a CI that spit back something like: "you will have a panic at line 156 when your input is > 4"
A model checker can do that!
See this
https://model-checking.github.io/kani/tutorial-kinds-of-fail...
Other techniques are also possible
https://github.com/viperproject/prusti-dev#quick-example
(Here I could link a lot of things, I just selected two Rust projects to illustrate)
This works better if you are able to provide contracts in your API that says which guarantees you provide. Alternatively, asserts are useful too.
-
Programming Languages Going Above and Beyond
You might be interested in the Prusti project, which statically checks for absence of reachable panics, overflows etc. It also allows user-defined specifications such as pre and post-conditions, loop body invariants, termination checking and so on.
https://github.com/viperproject/prusti-dev
-
Trying to find a crate that allows you to constrain the value of arguments in various ways via a proc macro
This is called refinement types and prusti might be the project you saw.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
But there's also a lot of exciting work around formal verification like Prusti.
-
Is there something like "super-safe" rust?
prusti
-
A plan for cybersecurity and grid safety
Efforts: seL4, Project Everest, the Prossimo project of the ISRG, Let's Encrypt, and Prusti for the Rust language
-
Prop v0.42 released! Don't panic! The answer is... support for dependent types :)
Wow that sounds really cool! I'm not an expert but does that mean that one day you could implement dependend types or refinement types in Rust as a crate ? I currently only know of tools like: Flux Creusot Kani Prusti
- Prusti: Static Analyzer for Rust
What are some alternatives?
time - The most used Rust library for date and time handling.
MIRAI - Rust mid-level IR Abstract Interpreter
tai - tai (Terminal Ascii Images) tool to convert images to text written in Rust
kani - Kani Rust Verifier
rustig - A tool to detect code paths leading to Rust's panic handler
Rudra - Rust Memory Safety & Undefined Behavior Detection
automem - C++-style automatic memory management smart pointers for D
no-panic - Attribute macro to require that the compiler prove a function can't ever panic
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
rust - Empowering everyone to build reliable and efficient software.