rust-orphan-rules
rust-by-example
Our great sponsors
rust-orphan-rules | rust-by-example | |
---|---|---|
11 | 66 | |
180 | 6,729 | |
- | 2.8% | |
0.0 | 8.5 | |
about 5 years ago | 3 days ago | |
Handlebars | ||
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.
rust-orphan-rules
- 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
rust-by-example
- Learning Rust for project.
-
A Beginner’s Guide to the Solana Web3 Stack
Rust can feel a bit intimidating at first but once you start getting the hang of it, you will enjoy it a lot. It has a very well articulated documentation, which can be used as a good learning resource too. Some other resources for Rust include Rustlings and Rust-By-Example.
-
Jumping into Rust for the first time. Is the interactive Rust textbook, published by the CS department at Brown University, a good starting point?
Rust by Example
-
How to move to rust from c++?
Rust by Example: Collection of runnable examples, which many find useful to read
-
Rust by Example: read lines - Why is the second example more efficient?
I think something went wrong there, I can find this (merged) PR with https://github.com/rust-lang/rust-by-example/pull/1679/files that has the first example collecting into a string, (which is obv less effective). It was merged 2 weeks ago. I dont know why it isnt online yet.
-
Picking Up Rust Before C With My Goals In Mind?
I more or less went straight from The Book (see also Rust by Example) to Learning Rust With Entirely Too Many Linked Lists and code::dive conference 2014 - Scott Meyers: Cpu Caches and Why You Care and I've often seen PNGme suggested as the next step after that.
-
How do I return a value from match construct?
Context around the "rust by example" discussion from 2015: https://github.com/rust-lang/rust-by-example/issues/390
-
From High-Level to Systems Programming: A Practical Guide to Rust, Part 2
The Rust By Example website is another helpful resource for learning Rust. It provides a series of interactive examples that demonstrate how to use various Rust features and libraries.
-
How to learn Rust (for backend) ?
The book is great and was my original introduction to the language, but rustlings or Rust By Example might be more interesting for an interactive (and more self paced) approach.
-
Learning rust
Rust by Example: Rust by Example is a collection of runnable examples that cover a wide range of Rust concepts and standard libraries. It's a great way to see how Rust code works in practice.
What are some alternatives?
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
pollster - A minimal async executor that lets you block on a future
book - The Rust Programming Language
keepass-rs - Rust KeePass database file parser for KDB, KDBX3 and KDBX4, with experimental support for KDBX4 writing.
zero-to-production - Code for "Zero To Production In Rust", a book on API development using Rust.
dislike-in-rust - A list of the few things I don't like about rust
monkey - Monkey patching in Go
getrandom - A small cross-platform library for retrieving random data from (operating) system source
RustBooks - List of Rust books
rust-delegate - Rust method delegation with less boilerplate
easy_rust - Rust explained using easy English