rust-orphan-rules

An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules (by Ixrec)

Rust-orphan-rules Alternatives

Similar projects and alternatives to rust-orphan-rules

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better rust-orphan-rules alternative or higher similarity.

rust-orphan-rules reviews and mentions

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.
  • Conflicting trait implementation, but there shouldn't be
    2 projects | /r/learnrust | 26 Apr 2023
  • Fellow Rust enthusiasts: What "sucks" about Rust?
    25 projects | /r/rust | 10 Mar 2023
    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
    5 projects | /r/gameenginedevs | 14 Feb 2023
    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?
    7 projects | /r/rust | 17 Nov 2022
    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)!
    4 projects | /r/rust | 14 Nov 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.
  • De/serialize an external crate's struct
    2 projects | /r/rust | 1 May 2022
    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.
  • Methods for Array Initialization in Rust
    2 projects | news.ycombinator.com | 24 May 2021
  • 🦀 Publishing My First Rust Crate
    3 projects | dev.to | 11 Jan 2021
    Need to keep a lot of things in mind to make sure your crate has great interoperability with the existing Rust ecosystem, e.g. because of the orphan rule the users of your crate won't be able to implement the traits defined in std or serde for the types from your crate, so you have to decide which ones it makes sense to implement and provide that implementation yourself.
  • A note from our sponsor - WorkOS
    workos.com | 28 Mar 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic rust-orphan-rules repo stats
11
174
0.0
about 5 years ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com