etl | GSL | |
---|---|---|
55 | 22 | |
1,956 | 5,956 | |
1.6% | 1.0% | |
9.6 | 5.9 | |
4 days ago | about 1 month 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.
etl
-
Modern C++ Programming Course
If you can't use the STL because of exceptions: https://www.etlcpp.com/
- How many of you do you actually use C++?
-
Undefined Behavior?
You can also use ETL (https://www.etlcpp.com)
-
As an embedded programmer which parts of C++ should I focus?
Use ETL for embedded standard library functionality: https://www.etlcpp.com/
-
C++ on embedded studio
The best choice here is use embedded Template Library: https://www.etlcpp.com/
-
C++20 for bare-metal microcontroller programming
If you can't get C++23, expected it's implemented in the ETL (it's also just a really amazing library for this kind of stuff - highly recommend!).
-
Recompile C++ Standard library to only include classes that are embedded system friendly
I want to use some of C++ std library classes/functions in my embedded system library project that I'm writing. However as the environment has limited ressources I don't want to have use or expose classes or functions that do the following: * Dynamic memory allocations * RTTI * Runtime exceptions I will be rewriting some basic container and algorithms according to my needs. I know that there are other re writes of STL like ESTL but I don't want to have any external dependencies So my question is can I somehow compile/package a fork of C++ std library that only include embedded systems friendly classes such as: - array - tuple - variant - type_traits Etc This compiled library must be completely standalone. The compiler that I use can support upto C++17 standard.
- Looking for well written, modern C++ (17/20) example projects for microcontrollers
-
What are some essential libraries for embedded systems everyone should learn?
I will never not recommend the Embedded Template Library
-
What programming language should I pick up as a senior developer ?
STL containers use dynamic memory allocation which is often a no-no in embedded contexts. there is the ETL https://www.etlcpp.com/ but I haven't used it!
GSL
-
60 terrible tips for a C++ developer
Already showed you how to use ranges and such above, gsl::final_action is here
-
Backward compatible implementations of newer standards constructs?
For span I would recommend the guideline support library - gsl::span
-
Hey Rustaceans! Got a question? Ask here (20/2023)!
Not sure how things are at this point so you might want to look up with those keywords, but a few years back clang-tidy was one of the suggested tools, or enabling the core guidelines checker in visual studio if you're using that. Maybe using GSL or something similar as well.
-
Hardening C++ with Bjarne Stroustrup
When I want safety guarantees, I use the original and run-time checked gsl::span, rather than std::span. https://github.com/microsoft/GSL .
-
I love building a startup in Rust. I wouldn't pick it again.
Another solution: use std::span (or some alternative implementations if the codebase doesn't use C++20).
-
C++23 “Pandemic Edition” is complete
If you ask me, the GSL [1] alone is a fairly radical departure from C++ that delivers a lot of safety. I don't know if it's gotten much popularity, though. Probably because it introduces a similar disruption like you might find from a brand new programming language.
[1] https://github.com/microsoft/GSL
-
Using Rust at a startup: A cautionary tale
> With Rust, though, one needs to learn entirely new ideas — things like lifetimes, ownership, and the borrow checker. These are not familiar concepts to most people working in other common languages ... Some of those “new” ideas are, of course, present in other languages — especially functional ones.
With C++, lifetime and ownership are just about as important but unfortunately no one's got your back. You can ignore lifetimes and ownership but you do so at your own peril. And the compiler won't tell you you're doing it wrong because the language wasn't designed for it to do so.
If you want a taste of rust's "mindset" (with respect to limitations imposed by some types) without jumping ship to a new language, try C++'s Guidelines Support Library [1]. It introduces some of the same benefits/friction as switching to rust but without a new language. Opting-in to some of these guidelines might be a gentler way to get some of the benefits of Rust. But it comes with a similarly higher bar.
[1] https://github.com/microsoft/GSL
- Passing a std:: array as a function parameter
-
I created a memory leak using smart pointers
It's also far more verbose than T* or T& (probably intentionally). If you really want a non-nullable pointer, gsl::not_null from the GSL is a good option. Writing your own version is also trivial, if you don't want to add a dependency.
-
I wanna go back to work at a car assembly plant
I instead use the GSL and the Core Guidelines, where
What are some alternatives?
EA Standard Template Library - EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
graphMat - A matrix header-only library, uses graphs internally, helpful when your matrix is part of a simulation where it needs to grow many times (or auto expand)
cppinsights - C++ Insights - See your source code with the eyes of a compiler
ordered-map - C++ hash map and hash set which preserve the order of insertion
sentry-native - Sentry SDK for C, C++ and native applications.
libsrt - libsrt is a C library for writing fast and safe C code, faster. It provides string, vector, bit set, set, map, hash set, and hash map handling. Suitable for soft and hard real-time. Allows both heap and stack allocation. *BETA* (API still can change: suggestions are welcome)
cpp-core-guidelines-cheatsheet - Cheatsheet for the C++ core guidelines, including a set of tried-and-true guidelines, rules, and best practices about coding in C++.
RxCpp - Reactive Extensions for C++
C-Golang-like-Defer - Cursed defer() method in C++ achieves similar results as Go's defer keyword.
Ygg - An intrusive C++17 implementation of a Red-Black-Tree, a Weight Balanced Tree, a Dynamic Segment Tree and much more!
score-simple-api-2