How to Bypass Rust's Orphan Rule
0 comments · rust
- Comments8
0 comments · rust
Story details from Lobsters ↗ · linked article on edvong.com.
How to Bypass Rust's Orphan Rule was first seen on Lobsters · Hottest on Nov 17, 2026. Since then it has appeared in 56 checks on 2 different days. Its best position was #3 of 25, reached on Nov 17, 21:21 UTC. It dropped off the list after Nov 18, 19:51 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Man this feels like AI writing. The sort of chipper statements and unhelpful metaphors (a tree of generic types is like a bunch of grapes?..). The concept is nice, but it's rough to read. Sorry if this isn't AI, these days it's tough to tell. :/
To refer to this as a bypass of the orphan rule would be mistaken as it would give the impression that this is an accident or emergent property of the language. Instead this is an intentional feature of Rust that was deliberately implemented in order to relax the orphan rule and make more programs expressible. This…
> For better or worse, we allow implementing foreign traits for foreign types. For example, impl `From<Foo> for Vec<i32>` is something any crate can write, even though `From` is a foreign trait, and `Vec` is a foreign type. WOW, that is a misleading first sentence. There is an unstated asterisk here: Rust allows…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 18, 19:51 UTC, after 2 days of trending.
#3 on Lobsters · Hottest, on Nov 17, 21:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 17, 2026 and has been on the list on 2 days (56 checks) since.