"if not this separator or not that separator" misunderstanding

What it does

lint for if condition (for multiple conditions that start by !) and path separator

Advantage

No response

Drawbacks

No response

Example

use std::{io::*, path::*};
fn main() {
    let mut s = String::new();
    stdin().read_line(&mut s).unwrap();
    if !s.ends_with('/') || !s.ends_with('\\') {
        panic!("Path must end by / or \\")
    }
    let p = Path::new(&s);
}

There's a misunderstanding in the if condition, someone may read if !s.ends_with('/') || !s.ends_with('\\') as "if not this separator or not that separator", and there's a constant MAIN_SEPARATOR in std::path, the better code may be:

use std::{io::*, path::*};
fn main() {
    let mut s = String::new();
    stdin().read_line(&mut s).unwrap();
    if !s.ends_with(MAIN_SEPARATOR) {
        panic!("Path must end by {MAIN_SEPARATOR}")
    }
    let p = Path::new(&s);
}

The issue names Rust examples and std::path::MAIN_SEPARATOR, but no source file or test is provided. Start by clarifying the intended lint behavior for the two negated ends_with checks and the platform separator. Done means the accepted condition is unambiguous and the behavior is covered by tests.