scope_guard
refl-cpp
Our great sponsors
scope_guard | refl-cpp | |
---|---|---|
3 | 3 | |
160 | 986 | |
- | - | |
3.7 | 0.0 | |
about 1 year ago | over 1 year ago | |
C++ | C++ | |
The Unlicense | MIT License |
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.
scope_guard
-
Building a Cloud Database from Scratch: Why We Moved from C++ to Rust
E.g. see this implementation: https://ricab.github.io/scope_guard/
But also I should make the point that you generally don't need to write defer-like statements at all when using RAII because it's implemented in the actual type. So it's only more code overall for types that are used only once or maybe twice.
-
Possible compiler error ?
Meanwhile I will check and use https://github.com/ricab/scope_guard
-
Is WebAssembly magic performance pixie dust?
> low level details leak into your high level description of code, making the two coupled. You can’t make them invisible.
It's your job to make it not to leak. You have to write Modern C++ wrappers around C libs.
Similarity, The same can be said for Java. You can do low level in Java.
C++ is not C. C++ has backward compatibility with C.
Look at Boost folks, they wrote a Modern C++ wrapper around a C HTTP parser.
> And as I said, I’m familiar with RAII, it’s really great when the given object is scope-based, but can’t do anything otherwise.
Nothing is impossible.
You can use Scope Exit Guard with QT Widget.
https://github.com/ricab/scope_guard
> And if the new subclass has some non-standard object life cycle you HAVE to handle that case somewhere else, modifying another aspect of the code. It is not invisible, unless you want leaking code/memory corruption.
Again, Scope Exit Guards solve your problem!
refl-cpp
-
Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224
You'd be surprised how much friction you'd have for C++ reflection. First, since it's a custom build step, you can do a mix of custom code gen and C++ constexpr/consteval for static reflection. Here's a header-only implementation for adding compile time reflection purely within the language [1]. And v8 already does dynamic code gen as part of its build process (to generate the snapshot to speedup instantiation of the isolate). Dynamic reflection is a must since JS is a dynamic language with reflection support.
Now of course, I don't know the specific details of reflection needed for the abstractions you reference and clearly V8 is still doing some amount of manual IR generation, so it's possible it would be a substantial investment to actually retrofit those techniques into v8. One would have to do a careful analysis of historical security exploits & specific techniques and their ability to prevent to figure out if it's worth adding those abstractions (especially since there is a potential performance tradeoff as you mention). As I said, I think there's insufficient research in this area to establish a compelling body of best practices (not to take away from the contributions of the GraalJS team to this space).
[1] https://github.com/veselink1/refl-cpp
-
C++ Reflection for Component Serialization and Inspection
I’ve been using https://github.com/veselink1/refl-cpp for my recent project where i needed reflections, especially for serialization. Cant wait for c++48 and reflections in standard
- Show HN: Static reflection for C++17 (enumeration, attributes, proxies, ...)
What are some alternatives?
maddy - C++ Markdown to HTML header-only parser library
svector - Compact SVO optimized vector for C++17 or higher
expected-lite - expected lite - Expected objects in C++11 and later in a single-file header-only library
entt - Gaming meets modern C++ - a fast and reliable entity component system (ECS) and much more
cpp-peglib - A single file C++ header-only PEG (Parsing Expression Grammars) library
crunchy-bytes - C++ 17 Schema Serialization Library
iswasmfast - Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js.
json - JSON for Modern C++
human-asmjs - Tips and tricks for writing asm.js as a human - Note: WebAssembly has replaced asm.js, so this is no longer maintained.
BLIB - Small organized collection of common code I have accumulated over the years that has amassed into a proper 2d game engine
influxdb-cpp - 💜 C++ client for InfluxDB.
zxorm - Zach's ORM - A C++20 ORM for SQLite