Skip to content

fix: no longer emit error for functions has no return statement under isolatedDeclarations - #58331

Closed
Jack Works (Jack-Works) wants to merge 1 commit into
microsoft:mainfrom
Jack-Works:gh-58330
Closed

Jack Works (Jack-Works) wants to merge 1 commit into
microsoft:mainfrom
Jack-Works:gh-58330

Conversation

@Jack-Works

Copy link
Copy Markdown
Contributor

Fixes #58330

@typescript-bot TypeScript Bot (typescript-bot) added the For Uncommitted Bug PR for untriaged, rejected, closed or missing bug label Apr 26, 2024

@jakebailey Jake Bailey (jakebailey) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jakebailey

Copy link
Copy Markdown
Member

#58330 was declined to give us the option to make function declarations and function expressions consistent in the future; going to close this one. Thanks for sending it, though.

@typescript-bot

Copy link
Copy Markdown
Contributor

The TypeScript team hasn't accepted the linked issue #58330. If you can get it accepted, this PR will have a better chance of being reviewed.

@microsoft 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

For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

isolatedDeclarations should not have warning for functions that have no return statements

4 participants