From 35a1f2fcfcb174f9dbe3775fc75cad140e97e55e Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Mon, 8 Jun 2015 12:39:14 -0800 Subject: Recategorize the floating-point operations "under consideration". min/max - Promote these to base; they are all trivially polyfillable, and are useful things to have in the base platform besides. nearestInt - This is not trivially polyfillable (JavaScript's Math.round does tie-breaking wrong), so put it in EssentialPostMVPFeatures.md so it can join floor/ceil. trunc - This is not trivially polyfillable (in ES6, but not in all the browsers we need the polyfill to support), so put it in EssentialPostMVPFeatures.md so it can join floor/ceil/nearestInt in providing rouding to integer via all the standard roundings. minNum/maxNum - Put these in FutureFeatures.md for future consideration. They're not trivially polyfillable, and they're not obviously essential at this point, though they do have uses. --- FutureFeatures.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'FutureFeatures.md') diff --git a/FutureFeatures.md b/FutureFeatures.md index e21cba7..5d60a04 100644 --- a/FutureFeatures.md +++ b/FutureFeatures.md @@ -224,3 +224,12 @@ use cases: * Int32SMax - signed maximum * Int32UMin - unsigned minimum * Int32UMax - unsigned maximum + +## Additional floating point operations + + * Float32MinNum - minimum; if exactly one operand is NaN, returns the other operand + * Float32MaxNum - maximum; if exactly one operand is NaN, returns the other operand + * Float64MinNum - minimum; if exactly one operand is NaN, returns the other operand + * Float64MaxNum - maximum; if exactly one operand is NaN, returns the other operand + +MinNum, and MaxNum operations would treat -0 as being effectively less than 0. -- cgit v1.2.3