[
https://issues.apache.org/jira/browse/NUMBERS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048519#comment-16048519
]
Bruno P. Kinoshita commented on NUMBERS-43:
-------------------------------------------
>(in these times where memory is not a scarce resources anymore)?
I think only when performance is an issue, users will want to have methods like
this available. This
[thread|https://softwareengineering.stackexchange.com/questions/316822/why-are-floats-still-part-of-the-java-language-when-doubles-are-mostly-recommend]
for instance contains several examples of why float is still included in the
JVM. From what I could tell, all the replies are about performance (memory,
CPU).
I'm -0 to removing the method. I think the cost to maintain it is low, and
while not really useful most of the times, there could be cases where users
running code in embedded hardware or - who knows - GPU's would prefer to keep
the data as float, and avoid creating doubles if necessary.
> Remove "round(float)" methods?
> ------------------------------
>
> Key: NUMBERS-43
> URL: https://issues.apache.org/jira/browse/NUMBERS-43
> Project: Commons Numbers
> Issue Type: Wish
> Reporter: Gilles
> Labels: api, float
> Fix For: 1.0
>
>
> In class {{Precision}}, there are methods for rounding {{float}} values, e.g.
> {code:java}
> public static float round(float x, int scale, int roundingMethod) { /* ... */
> }
> {code}
> Is there any use for supporting specific handling of floats (in these times
> where memory is not a scarce resources anymore)?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
