rust-orphan-rules
An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules (by Ixrec)
pollster
A minimal async executor that lets you block on a future (by zesterer)
Our great sponsors
rust-orphan-rules | pollster | |
---|---|---|
11 | 3 | |
180 | 441 | |
- | - | |
0.0 | 3.6 | |
about 5 years ago | 6 months ago | |
Rust | ||
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
rust-orphan-rules
Posts with mentions or reviews of rust-orphan-rules.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-26.
- Coherence and Orphan Rules in Rust: An unofficial, experimental place for docum
- Conflicting trait implementation, but there shouldn't be
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Well, unless someone comes up with better, compatible rules, the orpan rules are gonna stick around.
-
The langage for the next 40 years of engine dev
Additionally there are other issues with rust currently. Compile time code (ala constexpr) is not up to par with C++20 (not really close). The const generic aren't as powerful as C++20 which added non primitive non type template parameters (though with you stuck with C++14, it actually is significantly better than what you have, again, if you're going to use C++, just use 20). Generics accepting closures is a bit more of an ordeal in rust, compared to C++. Also C++'s Duck Typed templates allow for some uncharacteristically strong typing compared to what is expressible in Rust generics currently. Now, duck typed templates do have major downsides, for example the entire feature of concepts is completely irrelevant in rust, but required for sane DTT type bounds, but they also have major upsides. Rust currently doesn't have "negative trait bounds", basically "This objected does not implement this trait, or std::enable_if> or the equivalent concepts implementation. Rust also doesn't have trait specializations, basically template specialization. Do note all features I've talked about to this point have nightly options, they just are at various stages of being stable/complete. Another issue is the orphan rule, though this is kind of a problem in C++ too in some respects, and that's unlikely to change drastically, since there are legitimate reasons for it's existence. For a lot of code none of these things are big deals, others they are, which is why you find inconsistent feed back on these issues.
-
What are Rust’s biggest weaknesses?
Not that simple... hence why Orphan rule is still in-place. The struct wrapper was implemented in Rust as a temporary safe work-around. However, they are making progress on a solution: https://github.com/Ixrec/rust-orphan-rules/issues/1
-
Hey Rustaceans! Got a question? Ask here! (46/2022)!
That's still not an entirely complete explanation because there's more nuanced situations which aren't completely foreign but are foreign enough that if allowed, two crates could write the same impls. Some of the definitions are still unofficial as far as am I'm aware. For the best reference I’ve seen so far see this for more details.
-
Design Patterns with Rust Types
In our crate the compiler doesn't know when calling MyTrait methods on MyStruct whether to use the implementation defined in crate 3 or crate 4! Rust has a set of orphan rules to prevent this situation from happening.
-
De/serialize an external crate's struct
Sadly because of the rusts orphan rule you cannot implement a Trait on a Type where you do not own one or the other. So, apart from upstream contributions your only options are either a new Trait or a new Type.
-
Is the orphan rule the only solution?
If anyone is looking for additional background about orphan rules, check out https://github.com/Ixrec/rust-orphan-rules
- Methods for Array Initialization in Rust
pollster
Posts with mentions or reviews of pollster.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-08.
-
Rust criticism from a Rustacean
Other than that, I'm using async mostly not in a web-based environment, unlike your assumption that the "so-called web-devs" only want to use it. It's also quite flexible, you want it blocking? Start a blocking executor. You don't want tokio for that? Use a minimal executor like https://github.com/zesterer/pollster for that...
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Check out https://github.com/zesterer/pollster. This can be the solution to the async problem you described
-
Tachyonix: a very fast MPSC async bounded channel
Pollster: https://github.com/zesterer/pollster
What are some alternatives?
When comparing rust-orphan-rules and pollster you can also consider the following projects:
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
tachyonix - An asynchronous, multi-producer, single-consumer (MPSC) bounded channel that operates at tachyonic speeds
keepass-rs - Rust KeePass database file parser for KDB, KDBX3 and KDBX4, with experimental support for KDBX4 writing.
getrandom - A small cross-platform library for retrieving random data from (operating) system source
dislike-in-rust - A list of the few things I don't like about rust
rust-delegate - Rust method delegation with less boilerplate
SHLL - An experiment of high level code optimization
rust-by-example - Learn Rust with examples (Live code editor included)
storages-api
rust-orphan-rules vs cargo-release
pollster vs tachyonix
rust-orphan-rules vs keepass-rs
pollster vs getrandom
rust-orphan-rules vs dislike-in-rust
pollster vs rust-delegate
rust-orphan-rules vs getrandom
pollster vs dislike-in-rust
rust-orphan-rules vs rust-delegate
pollster vs SHLL
rust-orphan-rules vs rust-by-example
pollster vs storages-api