Feature Request: Allow default implementations of static methods in derived traits.

[Dretch]

I think it would be great if this sort of thing worked:

trait Shizzle {
    static fn shizzle();
}

trait Shozzle : Shizzle {
    static fn shizzle() {
        io::println(~"shizzle! " + shozzle::<self>());
    }
    static fn shozzle() -> ~str;
}

impl int : Shozzle {
    static fn shozzle() -> ~str { ~"i'm an int!" }
}

fn main() {
    shizzle::<int>();
}

Currently it fails with this error:

test-trait-inheritance.rs:12:4: 12:23 error: duplicate definition of value shizzle
test-trait-inheritance.rs:12     static fn shizzle() {
                                 ^~~~~~~~~~~~~~~~~~~
test-trait-inheritance.rs:5:4: 5:23 note: first definition of value shizzle here:
test-trait-inheritance.rs:5     static fn shizzle();
                                ^~~~~~~~~~~~~~~~~~~
error: aborting due to previous error

[Dretch]

Note that a similar pattern using non-static methods works as expected:

trait Shizzle {
    fn shizzle();
}

trait Shozzle : Shizzle {
    fn shizzle() {
        io::println(~"shizzle! " + self.shozzle());
    }
    fn shozzle() -> ~str;
}

impl int : Shozzle {
    fn shozzle() -> ~str { ~"i'm an int!" }
}

fn main() {
    2.shizzle();
}

(this compiles and runs)

[nikomatsakis]

I think this is more a side-effect of the scoping rules for static fns, which promote them to the parent module. If you enclosed Shizzle and Shozzle in different modules, it ought to work (modulo bugs). Those scoping rules are in the process of changing. Therefore, I am going to close this bug.