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 is why I enjoy embedded Rust: it makes you appreciate the joy of having a nice big ol’ heap to allocate into when you’re not programming microcontrollers
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.