Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

In addRange, don't check for undefined values; do support slice#16161

Closed
ghost wants to merge 1 commit into
mastermicrosoft/TypeScript:masterfrom
addRangemicrosoft/TypeScript:addRangeCopy head branch name to clipboard
Closed

In addRange, don't check for undefined values; do support slice#16161
ghost wants to merge 1 commit into
mastermicrosoft/TypeScript:masterfrom
addRangemicrosoft/TypeScript:addRangeCopy head branch name to clipboard

Conversation

@ghost

@ghost ghost commented May 31, 2017

Copy link
Copy Markdown

@ghost ghost requested a review from rbuckton May 31, 2017 00:28
@rbuckton

Copy link
Copy Markdown
Contributor

@Andy-MS, see https://github.com/Microsoft/TypeScript/pull/16120/files#diff-66cec844e251a1918deb897eabca206bR761. Plus, I would prefer we leave the undefined check in.

@ghost

ghost commented Jun 2, 2017

Copy link
Copy Markdown
Author

Could we use a Debug.assert instead of if for the undefined check?

@rbuckton

rbuckton commented Jun 6, 2017

Copy link
Copy Markdown
Contributor

I'd prefer not. Some of the transforms return undefined to indicate that the node should be elided. Since this is used mostly in the transforms, I'd rather be consistent.

@ghost ghost closed this Jun 6, 2017
@ghost ghost deleted the addRange branch June 6, 2017 20:31
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
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.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.