value literals act differently than literal type constants as indexes in index expressions

[zpdDG4gta8XKpMCd]

nightly build Oct 24, 2016

const values: [number, string] = [1, 'a'];

const one = values[0]; // number, OK

const index = 0; // index is `0` (not just a number)
const another = values[index]; // expected number, actual: string | number <-- WHY?

[mhegazy]

duplicate of #6678

[zpdDG4gta8XKpMCd]

no, i don't agree it's a dup

now we have constant primitives as literal types, wheras that item doens't say anything about it

in other words, at that time it was a big deal to do
now with literal types it should be trivial (already works for literal values)

[RyanCavanaugh]

This issue needs to be open because the other one hasn't been implemented yet? Please help me understand this

[zpdDG4gta8XKpMCd]

the other one was created a year ago and asking for something that didn't have a chassis to be made
this one just states the fact that 2 expressions of the exact same type give different results