typeguard stop applying for readonly properties of const variables in new closures

[cancerberoSgx]

See self-explanatory example

Like happens with const variable typeguards that keep applying inside new function-like bodies, I would expect the same for const object literal's readonly properties

[kitsonk]

TypeScript resets narrowing within the scope of a function because it cannot be sure that the outer scope checks are valid when the resulting function is invoked.

See #11498

[maxencefrenette]

Correct me if i'm wrong, but the combine use of readonly and const should guarantee that root.foo2 is not undefined. #11498 addresses the case when the root variable is not const of the property is not readonly.

[RyanCavanaugh]

Just because you have a readonly reference to an object doesn't mean someone else doesn't have a mutable reference to it

[maxencefrenette]

Ah, I didn't think of that. Thanks for the explanation.

[cancerberoSgx]

aja, got it thanks! Should I close this issue ?

[typescript-bot]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.