By string, I of course speak of string literals. The only place where this would be an issue is writing Rust compiler error messages. I don't consider that a st

By string, I of course speak of string literals. The only place where this would be an issue is writing Rust compiler error messages. I don't consider that a strong argument for why the path analogy should be broken. Because the path analogy is broken, modules in Rust have strange rules. For example, use foo::bar; doesn't actually use a relative "path" from the current module you need to use use self::foo::bar; I think this is a confusing default, and it would have never ended up this way if Rust used Windows-path-looking namespace syntax if you're writing a parser and manipulating actual arrays of bytes, you don't have an issue with backslash, it's just another character to you