semver-trick
708
semver-trick | 708 | |
---|---|---|
15 | 12 | |
414 | 80 | |
- | - | |
2.8 | 1.8 | |
23 days ago | over 2 years ago | |
Rust | C++ | |
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.
semver-trick
-
Making Rust supply chain attacks harder with Cackle
Let's say crate B depends on crate A with a pinned dependency, and uses one of its types in a public interface.
Crate C depends on them both. It now can't bring in updates to A until B does, and when B updates that's a breaking change, so it better bump its major version.
Take a look at this teick, for example, for foundational crates updating their major version: https://github.com/dtolnay/semver-trick
Now imagine that being an issue every single patxh update.
-
The module system is too confusing
Rust modules require a tiny bit more definition up-front, but they neatly decouple the module hierarchy from file layout so you can reorganize code however you like in future, and they support very fine grained control of privacy (such as being able to say pub(super) and pub(crate)). In extreme cases, you can even re-export symbols from one module in another without it counting as a breaking change, so you have even more options for evolving your project without breaking existing consumers. Look at the the semver trick as an example of how powerful this can be and how much freedom it gives library implementors. (And even if you're only a library consumer, wouldn't you rather be consuming libraries by implementors that had more freedom and power?)
-
My first year with Rust: The good, the bad, the ugly
A library author concerned about this can use the semver trick. TL;DR: if your current version is 0.42, you can do a 1.0 release, then do a 0.43 release that depends upon your 1.0 release and re-exports all the symbols.
-
Does Rust have any design mistakes?
I mean for all the parts of the standard library that do not change, one could presumably use the semver-trick.
-
Rust is hard, or: The misery of mainstream programming
The semver trick can help with libraries at least when they go to unify the ecosystem. Release new versions that replicate previous APIs in a compatible way while moving to the standard library implementation.
-
Roadmap
Because you still run into the problem that's been seen when various important crates upgraded and either didn't use the semver trick or had downstream crates specifying Cargo.toml version requirements too narrowly for it to be effective.
- The Rust SemVer Trick (2019)
-
This Year in Embedded Rust: 2021 edition
It's called the "semver-trick" [1].
[1]: https://github.com/dtolnay/semver-trick
- The Semver Trick
-
The chip shortage keeps getting worse. Why can't we just make more?
The JVM is 114MiB on my machine. A near-minimal ggez program in debug mode is about 100MiB,¹ and ggez is small for a Rust application library. When you start getting into the 300s of dependencies (i.e. every time I've ever got beyond a trivial desktop application), you're lucky if your release build is less than 100MiB.
Sure, I could probably halve that by forking every dependency so they aren't duplicating versions, but that's a lot of work. (It's a shame Rust doesn't let you do conditional compilation based on dependency versions, or this would be a lot easier. As it is, we have to resort to the Semver trick: https://github.com/dtolnay/semver-trick/ — not that many people do that, so it's functionally useless.)
¹: I can get it down to around 8MiB with release mode, lto etc., but that significantly increases the build time and only about halves the weight of the intermediate build files.
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
What are some alternatives?
lang-team - Home of the Rust lang team
dyno - Runtime polymorphism done right
cargo-llvm-lines - Count lines of LLVM IR per generic function
rust-base64 - base64, in rust
mold - Mold: A Modern Linker 🦠
Thruster - A fast, middleware based, web framework written in Rust
rust - Empowering everyone to build reliable and efficient software.
rust-quiz - Medium to hard Rust questions with explanations
STL - MSVC's implementation of the C++ Standard Library.
serde - Serialization framework for Rust
rfcs - RFCs for changes to Rust