On Dec 17, 2014, at 2:26 AM, Andreas Lundblad <[email protected]>
wrote:
> Right. As it stands now the class level description says "the semantics of
> the conversion is defined by the Number implementation in question", and then
> the documentation of longValue narrows this down to "rounding or truncation".
> By adding "or some other narrowing conversion" we make room for the
> BigDecimal/BigInteger implementations, but I would argue that it's still more
> constrained than the class level description.
>
> Another suggestion would be:
>
> "Returns the value of the specified number as a {@code long}. The specific
> semantics of the conversion is defined by the subclass in question."
This seems reasonable to me. I’ll put together a patch to this effect unless
there are other suggestions.
Thanks,
Brian
