Is the CLR capable of static interfaces?

Question

And if so, why can't you do this:

public interface IParsable
{
    static IParsable Parse(string s);
    static bool TryParse(string s, out IParsable);
}

in c #?

EDIT: Or, alternatively:

public interface IParseable<T>
{
    static T Parse(string s);
    static bool TryParse(string s, out T);
}

EDIT No. 2: I found out the stupidity of my paths by trying to use IParsable, as suggested by many below. The following example. Of course, there is no way to allow the TryParse call ...

public IParsable ReadFromKeyboard()
{
    IParsable ToReturn;
    bool FirstTry = false;
    bool Success;
    do
    {
        if (!FirstTry)
            DisplayError();
        AskForInput();

        Success = IParsable.TryParse(Console.ReadLine, out ToReturn);
        FirstTry = false;
    } while(!Success)

    return ToReturn;
}

Answer 1

No, the CLR does not have such a thing as static interfaces. I suggested that they would be useful for generic type constraints, but this is the only thing I see for them ... otherwise, how would you use it IParsablein your example? How would you skip a type that could parse it?

. , .

Answer 2

, .

Answer 3

CLR . .

- , , CLR (, ).

, ( ) : . .

Answer 4

, . :

. , . .

Answer 5

# , - . , virtual ( ) .

, . , , .

, , , , . .

Answer 6

, CLR . , .

Other similar functions that .NET (well, C #) do not have: Haskell class classes , F # element restrictions for generic types