Title:
[ANeff] ER for: BigDecimal/precisionEvaluate() by default, or per-app setting
| View in TrackerStatus/Resolution/Reason: To Fix//
Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff ()
Created: 08/18/2017
Components: Language
Versions: 2016
Failure Type: Others
Found In Build/Fixed In Build: /
Priority/Frequency: Normal /
Locale/System: / Platforms All
Vote Count: 0
This ER is for: BigDecimal/precisionEvaluate() by default, or per-app setting
Suggestions:
1) Store numbers as BigDecimal, instead of Double
-or-
2) Do precisionEvaluate() behind-the-scenes when calculation involves a floating point number
-or-
3) Add per-app setting to specify BigDecimal as number data type
Who doesn't want more precision easier? Manually using precisionEvaluate() all over is annoying. If there is a big performance hit, then I suggest #3 as it is opt-in. If small peformance hit, then #1 or #2.Attachments:
Comments: