Skip to content

unary negation of undefined (no match) should return undefined #124

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.

Sign up for GitHub

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

Jump to bottom
Merged
mattbaileyuk merged 3 commits into from
Jan 18, 2018
Merged

unary negation of undefined (no match) should return undefined #124

mattbaileyuk merged 3 commits into from
Jan 18, 2018

Conversation

@andrew-coleman
Copy link
Member

@andrew-coleman andrew-coleman commented Jan 18, 2018

resolves #99

When handling the unary negation operator -, let undefined (no match) pass through.

@coveralls
Copy link

coveralls commented Jan 18, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 100.0% when pulling 73dcb90 on negation into 5fc1c94 on master.

@coveralls
Copy link

coveralls commented Jan 18, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 100.0% when pulling 73dcb90 on negation into 5fc1c94 on master.

@coveralls
Copy link

coveralls commented Jan 18, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 100.0% when pulling 292dfca on negation into 557249e on master.

@mattbaileyuk mattbaileyuk merged commit 7f3adf6 into master Jan 18, 2018
@mattbaileyuk mattbaileyuk deleted the negation branch January 18, 2018 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mattbaileyuk mattbaileyuk mattbaileyuk approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Handling of "undefined" input to negate operator is inconsistent?

4 participants

@andrew-coleman @coveralls @mattbaileyuk