Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Actually, I think Borrow targets should be marked. Obviously that ship had sailed with Rust 1.0, but it would fix a ton of problems like this. For one, all statements of the type
impl<T: Borrow<U>, U: Borrowed> Borrow<U> for MyPtr<T>
would become valid because it can be statically known that MyPtr doesn't implement Borrowed because it doesn't make sense to borrow up to but not through a smart pointer.
I finally got it working! Now I have a foundation for a kernel and an uefi bootloader written in pure Rust
To...
I can't tell if I didn't understand an important detail about Rust traits or the system is badly underdesigned, but I keep bumping into situations where the most general correct implementation of an std trait on a container clashes with one of the std implementations, and I would need a very obvious negative statement to make them mutually exclusive (for example that T in MyPtr<T> can never implement Borrow<MyPtr<T>>)
rant
rust
traits