dodrio
scope_guard
| dodrio | scope_guard | |
|---|---|---|
| 1 | 3 | |
| 1,200 | 185 | |
| - | - | |
| 2.2 | 3.7 | |
| almost 4 years ago | almost 2 years ago | |
| Rust | C++ | |
| Mozilla Public License 2.0 | The Unlicense |
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.
dodrio
-
Is WebAssembly magic performance pixie dust?
Doesn't seem to stop MS with Blazor (.Net), Rust, and a few others from doing this. Also, there are plenty of games running in web assembly using bindings for things like WebGL and openal via similar bindings. As far as I know the current situation is pretty workable already and getting better. E.g. garbage collection is coming pretty soon.
I guess it depends on what you are doing. For most people doing web assembly, the point is avoiding dealing with/minimizing the need for interacting with javascript. But still, it seems there are some nice virtual dom options for Rust: https://github.com/fitzgen/dodrio that are allededly fast and performant (not a Rust programmer myself).
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!