String method is wrongly allowed as a type

TypeScript Version: nightly (2.1.0-dev.20161110)

Code

// @Filename: a.d.ts
declare const x: "foo".charCodeAt(0);

Expected behavior:

An error; probably a syntax error.

Actual behavior:

x is of type number -- the return type of charCodeAt.

DIscovered at DefinitelyTyped/DefinitelyTyped#12603 (comment).

[DanielRosenwasser]

...did someone accidentally implement #6606?

interface String {
    typeof<T>(x: T): T
}

class C {
    foo() {
        var x: "".typeof(this.foo);
    }
}

var nodes = document.getElementsByTagName('li');
type ItemType = "".typeof(nodes.item(0));

This only happens when the type starts with a string literal, so it probably has something to do with string literal types.

[DanielRosenwasser]

Actually it works with numeric literals as well

interface Number {
    typeof<T>(x: T): T
}

class C {
    foo() {
        var x: 3.141592.typeof(this.foo);
    }
}

var nodes = document.getElementsByTagName('li');
type ItemType = 4..typeof(nodes.item(0));

Same with true and false:

interface Boolean {
    typeof<T>(x: T): T
}

class C {
    foo() {
        var x: false.typeof(this.foo);
    }
}

var nodes = document.getElementsByTagName('li');
type ItemType = true.typeof(nodes.item(0));

[SamPruden]

Can we leave this in the language until #6606 lands? It's fun. 😂 See #6606 (comment)

[DanielRosenwasser]

@TheOtherSamP I'm sorry. While I love hacky terrible stuff that shouldn't work in the first place, I highly suggest you don't take a dependency on this in any serious manner. Last I tried, it already broke in a lot of the ways that make #6606 hard to implement anyway.

[SamPruden]

@DanielRosenwasser Okay, fine, I'll be good.

It's supposedly been in the language since at least November 2016, and I spotted it 2 hours before it got a PR. grumbles 😂