Level up your Rust skills.
Whenever I encounter an interesting Rust programming technique, I add it to this blog post. I’ve amassed a bit of a collection. Hopefully someone finds it interesting and useful!
You must log in or register to comment.
- 0 users online
- 2 users / day
- 2 users / week
- 2 users / month
- 74 users / 6 months
- 1 subscriber
- 258 Posts
- 707 Comments
- Modlog
In tip #3 I don’t see any benefit of doing impl AsRef<[T]> over &[T]
@calcopiritus @hatchet That way you can pass a reference or anything that can be turned into a reference as an argument. So the caller can supply a &T, Box<T>, Rc<T>, Arc<T>, … (I dont’t know if there is a blanket impl so that even T itself will work.
Well, actually I would tend to agree that &[T] is preferable to AsRef in most cases; all of the smart pointers you mentioned can also easily be turned into plain references. I probably could have chosen a better example.
These are actually nice, thanks!
Nice job! I’d add that the target of the Rustdoc link shortcuts can be customized, in case they are not autodetected or point to an undesired location, like so:
That will make the word Tool point to that type (note that the namespaces there - in lib::types::Tool - are relative to the current module / context, so you can use an imported name directly there too, for example).
Bookmarked :)