CIDLib
sanitizers
Our great sponsors
| CIDLib | sanitizers | |
|---|---|---|
| 35 | 48 | |
| 208 | 10,796 | |
| - | 2.1% | |
| 0.0 | 6.3 | |
| over 2 years ago | 3 days ago | |
| C++ | C | |
| MIT License | 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.
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?
sanitizers
-
Good resources for learning C in depth?
AddressSanitizer is really useful, it's similar to Valgrind but has much lower overhead.
-
Memory Allocators
And if you're up for it, I'd further recommend adding some ways to deal with buffer overflows in debug builds. The way I deal with this is by using Address-Sanitizer's manual poisoning api. Bonus point if you leave additional poisoned space between allocations so off by one errors are likely to end up in a poisoned region instead of nearby allocation.
- Exception thrown: write access violation
-
2023 Stack Overflow Survey: Rust is the most admired programming language, making it the most loved language for 8 years in a row
It also doesn't hurt that Miri can find many kinds of unsafe violations even in unsafe blocks. Zig may get something like this one day, but even if it does, checking things at runtime is not a substitute for compile time -- the C++ Sanitizers haven't exactly solved the safety story for C++ even over a decade later.
-
What's the best thing you've found in code? :
This is where stuff like ASan is really useful.
-
how do I check my library for memory leaks?
Use: https://github.com/google/sanitizers/wiki/AddressSanitizer
-
Is malloc_trim() safe to use?
Have you tried using tools like ASAN/LSAN or valgrind to confirm that there are indeed no memory leaks?
-
Having trouble with projects too long to post here.
Compile with ASAN and UBSAn
- Strange Segmentation Fault when accessing a Class inside a for loop.
- Will Carbon Replace C++?
What are some alternatives?
vulkan-guide - Introductory guide to vulkan.
miri - An interpreter for Rust's mid-level intermediate representation
kanzi-cpp - Fast lossless data compression in C++
spdlog - Fast C++ logging library.
NetFabric.Hyperlinq - High performance LINQ implementation with minimal heap allocations. Supports enumerables, async enumerables, arrays and Span<T>.
xeus-cling - Jupyter kernel for the C++ programming language
going-native-py - Bringing the power, stability and functional capabilities of C++ to Python.
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀
cmake-init-executable - Example executable output of cmake-init
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
cmake-init - The missing CMake project initializer
doctest - The fastest feature-rich C++11/14/17/20/23 single-header testing framework