aboutsummaryrefslogtreecommitdiff
path: root/FutureFeatures.md
diff options
context:
space:
mode:
authorDan Gohman <sunfish@mozilla.com>2015-06-08 12:39:14 -0800
committerDan Gohman <sunfish@mozilla.com>2015-06-12 14:26:17 -0700
commit35a1f2fcfcb174f9dbe3775fc75cad140e97e55e (patch)
tree7b6e9240a62c57749f355093e9fea749f3cb217b /FutureFeatures.md
parent3b9e3d2c99f071899c25765ba30ec36693f4a7fc (diff)
downloadnanowasm-design-35a1f2fcfcb174f9dbe3775fc75cad140e97e55e.tar.gz
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.
Diffstat (limited to 'FutureFeatures.md')
-rw-r--r--FutureFeatures.md9
1 files changed, 9 insertions, 0 deletions
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.