| 708 | rfcs | |
|---|---|---|
| 12 | 1 | |
| 80 | 0 | |
| - | - | |
| 1.8 | 10.0 | |
| over 2 years ago | about 3 years ago | |
| C++ | Shell | |
| Apache License 2.0 | Apache License 2.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
rfcs
-
Does Rust have any design mistakes?
Ok, there seems to be an existing RFC for this. It might be a good addition which doesn't seem to cause much change to the language and type system.
What are some alternatives?
dyno - Runtime polymorphism done right
lang-team - Home of the Rust lang team
mold - Mold: A Modern Linker 🦠
rust - Empowering everyone to build reliable and efficient software.
semver-trick - How to avoid complicated coordinated upgrades
STL - MSVC's implementation of the C++ Standard Library.
TablaM - The practical relational programing language for data-oriented applications
linux - Linux kernel source tree
qvgmsplit - Qt-based libvgm frontend for parallelized per-channel dumping
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
STC - A modern, user friendly, generic, type-safe and fast C99 container library: String, Vector, Sorted and Unordered Map and Set, Deque, Forward List, Smart Pointers, Bitset and Random numbers.