CIDLib
miri
Our great sponsors
| CIDLib | miri | |
|---|---|---|
| 35 | 120 | |
| 208 | 3,931 | |
| - | 2.3% | |
| 0.0 | 10.0 | |
| over 2 years ago | about 10 hours ago | |
| C++ | Rust | |
| MIT License | Apache License 2.0 |
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.
CIDLib
- Remaining Relevant Over Four Decades
-
When Zig is safer and faster than (unsafe) Rust
It's open source. It's in two parts CIDLib, which is the general purpose layer: https://github.com/DeanRoddey/CIDLib/
- Using Exceptions for all Error Handling.... in Theory
- The Cargo Cult of Good Code
- Do any of you use python or another scripting language instead of a build system?
- Why C++ devs earn so much more than js and python?
- C++ Developers of Reddit, tell your story
- 30,000 hours
- Systems Programming & Memory Safety
- Can't modern c++ be as safe as rust?
miri
-
RFC: Rust Has Provenance
Provenance is a dynamic property of pointer values. The actual underlying rules that a program must follow, even when using raw pointers and `unsafe`, are written in terms of provenance. Miri (https://github.com/rust-lang/miri) represents provenance as an actual value stored alongside each pointer's address, so it can check for violations of these rules.
Lifetimes are a static approximation of provenance. They are erased after being validated by the borrow checker, and do not exist in Miri or have any impact on what transformations the optimizer may perform. In other words, the provenance rules allow a superset of what the borrow checker allows.
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
-
Running rustc in a browser
There has been discussion of doing this with MIRI, which would be easier than all of rustc.
-
Piecemeal dropping of struct members causes UB? (Miri)
This issue has been fixed: https://github.com/rust-lang/miri/issues/2964
- Erroneous UB Error with Miri?
-
I've incidentally created one of the fastest bounded MPSC queue
Actually, I've done more advanced tests with MIRI (see https://github.com/rust-lang/miri/issues/2920 for example) which allowed me to fix some issues. I've also made the code compatible with loom, but I didn't found the time yet to write and execute loom tests. That's on the TODO-list, and I need to track it with an issue too.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
He is one of the big brains behind Miri, which is a interpreter that runs on the MIR (compiler representation between human code and asm/machine code) and detects undefined behavior. Super useful tool for language safety, pretty interesting on its own.
-
Formal verification for unsafe code?
I would also run your tests in Miri (https://github.com/rust-lang/miri) to try to cover more bases.
-
Ouroboros is also unsound
You can run miri and it will tell you if the given run triggered any undefined behavior. It will not analyze it for every possible use of the code, but checking for the presence of this specific issue using it should be fairly simple.
-
From Stacks to Trees: A new aliasing model for Rust
If you do encounter a piece of code on which TB performs much worse than SB, do submit it as an issue! There was one recently and we massively improved TB performance on this case by improving garbage collection.
What are some alternatives?
vulkan-guide - Introductory guide to vulkan.
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
kanzi-cpp - Fast lossless data compression in C++
cons-list - Singly-linked list implementation in Rust
NetFabric.Hyperlinq - High performance LINQ implementation with minimal heap allocations. Supports enumerables, async enumerables, arrays and Span<T>.
rust - Empowering everyone to build reliable and efficient software.
going-native-py - Bringing the power, stability and functional capabilities of C++ to Python.
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
cmake-init - The missing CMake project initializer
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
cmake-init-executable - Example executable output of cmake-init
rfcs - RFCs for changes to Rust