You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I'm getting the impression from the compiler that if I want a struct with a path in it, I should really use a PathBuf - you can't use Path, it's !Sized - using &Path means you now need lifetimes everywhere - why does Path::new return &Path?
This generalizes to anything that uses the borrowed/owned (and usually growable) patterns. Vec over slice, String over str, PathBuf over Path, OsString over OsStr, etc. If your struct has references as fields, you should have a very good reason
