When seeing if I could make reasonable use of rstest for time, I quickly ran into an issue. If a case parameter is the same as the function name, compilation will fail. For example,

#[rstest]
#[case(Sunday, Monday)]
fn next(#[case] day: Weekday, #[case] next: Weekday) {
    assert_eq!(day.next(), next);
}

This fails because next is both a case parameter and the function name, and it is ambiguous in the expansion:

#[cfg(test)]
fn next(day: Weekday, next: Weekday) {
    assert_eq!(day.next(), next);
}
#[cfg(test)]
mod next {
    use super::*;
    #[test]
    fn case_1() {
        let day = Sunday;
        let next = Monday;
        next(day, next)
    }
}

However, if next(day, next) is instead super::next(day, next), compilation would succeed. Given that the module is generated by rstest, we know that this path is always correct. Would it be possible to add this prefix to support the edge case?

Thanks for maintaining this crate!