Skip to content

🤖 User test baselines have changed #28076

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 23, 2018

Conversation

typescript-bot
Copy link
Collaborator

Please review the diff and merge if no changes are unexpected.
You can view the build log here.

cc @weswigham @sandersn @RyanCavanaugh

Copy link
Member

@weswigham weswigham left a comment

Choose a reason for hiding this comment

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

@sandersn this seems minor; but I don't know if it was a change to us or uglify.

@sandersn
Copy link
Member

No new version of uglify since August 30, so probably us. The error change is in an auto type, which we recently changed. You and @ahejlsberg worked on that, right? Can you figure out if the change is OK?

@weswigham
Copy link
Member

Oh yeah, totally then. All we did was stop making bad inferences to the auto tyoes in return positions.The new error is correct, since it's only actually assigned within the extract_args call, which we can't analyze inline (and is only conditionally called anyway)

@sandersn sandersn merged commit 3c5f1a6 into microsoft:master Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants