708
dyno
| 708 | dyno | |
|---|---|---|
| 12 | 11 | |
| 80 | 947 | |
| - | - | |
| 1.8 | 0.0 | |
| over 2 years ago | almost 3 years ago | |
| C++ | C++ | |
| Apache License 2.0 | Boost Software License 1.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.
708
-
CppFront Parameter Passing Semantics
Herb's parameter passing paper describes five parameter semantics categories (in, inout, out, move, and forward) to replace C++'s parameter passing styles (value, reference, const reference, r-value reference, and forwarding reference). And it poses the question of how parameter passing semantics can reasonably be made visible at the call-site.
-
Does Rust have any design mistakes?
Another design mistake, imho, is that Rust does not have Herb Sutter’s parameter passing style from his 708 paper. For example, out parameters instantly remove almost all use-cases for MaybeUninit, adding strong compiler guarantees and requiring zero unsafe code.
-
Is C++ Doomed?
In my C++ code, I've copied Rust and expressed fallible initialization by returning a std::optional from a static method (which the article failed to mention). The problem is that (like Rust) you lose placement initialization, and (unlike C++ or Rust) you can't initialize private fields using aggregate initialization or initializer lists, and must write a passthrough constructor (which can't even be private because it breaks make_unique).
https://github.com/hsutter/708 is a C++ proposal which unifies placement constructors and writable out-parameters ("definite first use"). I don't think it makes placement initialization fallible, but I'm not sure.
-
const all the things?
As noted elsewhere - we need in/out/forward.
- Three reasons to pass std::string_view by value
-
Last reference as rvalue?
There is a proposal by Herb Sutter (708: Parameter passing -> guaranteed unified initialization and unified value-setting) that want to do just that.
-
Experience C++ developers: do you enjoy using C++ (even for personal/hobby projects?)
Having said this, I can't wait for the dream to become reality
-
Is pass-by-value slower than pass-by-rvalue-reference?
I am waiting for this to become reality, and C++ language to suddenly lose 98% of its annoyingness!
-
All C++20 core language features with examples
Oh! That would be so nice. I mean, there is a proposal in the works, but I really doubt it will be adopted as it is.
- Proposal idea : attribute to force value assignment to default-constructible member in constructor
dyno
- DynaMix 2.0.0 Released
-
rust-like traits on plain C++ with short macro (type erasure actually)
Or dyno or Poly or Not-Actually-Boost.TE or ...
- C++ Polymorphism Without Inheritance Using Glaze
-
Potential C++ extension for type erasure as a language feature
Sean's tweet looks like something else from what I'm asking (not sure what to call it), as it evidently still uses inheritance (see int: IFace) and it needs an association between the two, but what I'm asking for is just pure uncoupled adaptation, no extra odd keywords like dyn and impl, no inheritance. Go interfaces and that dyno library look the most like it.
- Dyno: Runtime Polymorphism Done Right
-
C++20 library for modern dynamic polymorphism (virutal functions / std::any / std::proxy / and some std::variant current use cases replacement). AMA about it
Reminds me of Louis Dionne's Dyno
-
What is your C++?
If I need runtime polymorphism, I prefer to use something like Louis Dionne's Dyno (https://github.com/ldionne/dyno) when I can to maintain value semantics.
-
CppDyn: A simpler runtime polymorphism in C++
How does it compare to Louis Dionne's dyno? https://github.com/ldionne/dyno
- Experience C++ developers: do you enjoy using C++ (even for personal/hobby projects?)
-
vector of objects
Sounds similar to dyno.
What are some alternatives?
lang-team - Home of the Rust lang team
te - C++17 Run-time polymorphism (type erasure) library
mold - Mold: A Modern Linker 🦠
modern-cpp-tutorial - 📚 Modern C++ Tutorial: C++11/14/17/20 On the Fly | https://changkun.de/modern-cpp/
rust - Empowering everyone to build reliable and efficient software.
C++ Middleware Writer - The repo contains library code to support messaging and serialization. There are also two programs in the repo that are needed to use the CMW.
semver-trick - How to avoid complicated coordinated upgrades
CppDyn - CppDyn is a library which aims to simplify use of polymorphism in C++20
STL - MSVC's implementation of the C++ Standard Library.
hana - Your standard library for metaprogramming
rfcs - RFCs for changes to Rust
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.