Skip to content

Conversation

@jakebailey
Copy link
Member

Closes #44727, which was actually fixed by #57772.

@jakebailey
Copy link
Member Author

That or it's not fixed, if this type were to be inferred somehow?

@jakebailey jakebailey requested a review from weswigham April 15, 2024 22:58
@weswigham
Copy link
Member

That or it's not fixed, if this type were to be inferred somehow?

If you add a , prop = [null as any as BrokenType<any>][0] does it repro? Looks like it does on the playground.

@jakebailey
Copy link
Member Author

Sure does, so, not fixed. Oh well!

@jakebailey jakebailey closed this Apr 16, 2024
@jakebailey jakebailey deleted the fix-44727 branch April 16, 2024 00:11
@weswigham
Copy link
Member

If you want a fix, the first block in the old related PR (replacing Independent type parameters in the emit with unknown) is probably still the way to go; I don't think the emit's changed all that much.

@jakebailey jakebailey restored the fix-44727 branch April 16, 2024 01:52
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Declaration emit incorrectly prints uninstantiated generic type

2 participants