Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Implement new min/max semantics #80

Merged
merged 2 commits into from Oct 27, 2014
Merged

Conversation

sunfishcode
Copy link
Member

Following the proposal in
#67

These min and max functions follow the Math.min and Math.max semantics,
and are arguably the more intuitive and semantics.

This patch also introduces minNum and maxNum functions, which follow the
IEEE-754 minNum and maxNum semantics.

Following the proposal in
tc39#67

These min and max functions follow the Math.min and Math.max semantics,
and are arguably the more intuitive and semantics.

This patch also introduces minNum and maxNum functions, which follow the
IEEE-754 minNum and maxNum semantics.
@huningxin
Copy link
Contributor

LGTM. Thanks for the PR. Just one nit, would you like to add test cases for minNum and maxNum?

@sunfishcode
Copy link
Member Author

Thanks for spotting that. I added tests now, which turned up a copy+pasto bug in SIMD.float64x2.minNum!

johnmccutchan added a commit that referenced this pull request Oct 27, 2014
Implement new min/max semantics
@johnmccutchan johnmccutchan merged commit 4cf7dc6 into tc39:master Oct 27, 2014
@sunfishcode sunfishcode deleted the minmax branch February 14, 2015 04:00
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.

None yet

3 participants