inconsistencies with string literal values after always use literal types pr

[zpdDG4gta8XKpMCd]

nightly build jan 26

interface Wrapped<T> {
    wrapped: T;
}
function wrap<T>(value: T): Wrapped<T> {
    return { wrapped: value };
}

const one = 'test'; // one is 'test'
const oneWrapped = wrap(one); // oneWrapped is Wrapped<string>

const another: 'test' = 'test'; // another is 'test'
const anotherWrapped = wrap(another); // anotherWrapped is Wrapped<'test'> <--- WHY?

is that how #10676 supposed to work?

[zpdDG4gta8XKpMCd]

@ahejlsberg you might be interested

[mhegazy]

is that how #10676 supposed to work?

yes. the inferred literal type is not widened in two cases, 1. it is present unwrapped in the output, e.g. identity function, 2. if the type parameter is constraint to its base type, e.g. string. explicit literal types are never widened.

[zpdDG4gta8XKpMCd]

this is super counterintuitive

[mhegazy]

There is a long discussion in and in #10676,
#10898 and #11126 about why it does work this way. all other options were less intuitive overall.

[zpdDG4gta8XKpMCd]

i missed #11126 somehow, closing