Skip to content

stricter type checking of numeric operands #280

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 1 commit into from
Dec 3, 2018
Merged

stricter type checking of numeric operands #280

mattbaileyuk merged 1 commit into from
Dec 3, 2018

Conversation

@andrew-coleman
Copy link
Member

@andrew-coleman andrew-coleman commented Dec 2, 2018

Perform type checking on numeric operators before the 'undefined test' is done. More consistent with function type checking.

resolves #242

@coveralls
Copy link

coveralls commented Dec 2, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 69d2e1b on operand_types into c1721bf on master.

2 similar comments
@coveralls
Copy link

coveralls commented Dec 2, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 69d2e1b on operand_types into c1721bf on master.

@coveralls
Copy link

coveralls commented Dec 2, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 69d2e1b on operand_types into c1721bf on master.

@mattbaileyuk mattbaileyuk merged commit 7c229c9 into master Dec 3, 2018
@mattbaileyuk mattbaileyuk deleted the operand_types branch December 3, 2018 22:39
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.

Range operator allows invalid expressions

4 participants

@andrew-coleman @coveralls @mattbaileyuk