Skip to content

Improve Infinity handling in Math.min/max methods #452

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

Closed

Conversation

galpeter
Copy link
Contributor

In Math.max case: if we already found an infinity value update the result
only when the previous value was a negative infinity.

In Math.min case: if we already found an infinity value update the result
only when the previous value was a positive infinity.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com

In Math.max case: if we already found an infinity value update the result
only when the previous value was a negative infinity.

In Math.min case: if we already found an infinity value update the result
only when the previous value was a positive infinity.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com
@galpeter galpeter added bug Undesired behaviour ecma builtins Related to ECMA built-in routines labels Jul 22, 2015
@galpeter galpeter added this to the ECMA builtins milestone Jul 22, 2015
@galpeter
Copy link
Contributor Author

Fixes issue: #414

@dbatyai
Copy link
Member

dbatyai commented Jul 23, 2015

lgtm

@egavrin
Copy link
Contributor

egavrin commented Jul 24, 2015

Good to me

@galpeter
Copy link
Contributor Author

Landed: b5de03a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Undesired behaviour ecma builtins Related to ECMA built-in routines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants