On 07/18/2013 09:29 PM, sebb wrote:
> On 18 July 2013 19:54, Gilles wrote:
>> Hi.
>>
>>
>> On Thu, 18 Jul 2013 19:02:34 +0100, sebb wrote:
>>>
>>> On 18 July 2013 17:56, Mark Thomas wrote:
sebb wrote:
> The MATH code base currently generates hundreds of boxing warnings.
>
[...]
Maybe I'm missing something but: Isn't auto-boxing supposed to
be a feature?
Yes, of course, but the feature is not without its drawbacks as I
already mentioned.
- conversion overhead
- unexpected NPE when unboxing
- ambiguous remove() behaviour
For example:
x=1
list.remove(x);
Does that
On 18 July 2013 20:42, Phil Steitz wrote:
> On 7/18/13 12:29 PM, sebb wrote:
>> On 18 July 2013 19:54, Gilles wrote:
>>> Hi.
>>>
>>>
>>> On Thu, 18 Jul 2013 19:02:34 +0100, sebb wrote:
On 18 July 2013 17:56, Mark Thomas wrote:
> sebb wrote:
>
>> The MATH code base currently gen
On 7/18/13 12:29 PM, sebb wrote:
> On 18 July 2013 19:54, Gilles wrote:
>> Hi.
>>
>>
>> On Thu, 18 Jul 2013 19:02:34 +0100, sebb wrote:
>>> On 18 July 2013 17:56, Mark Thomas wrote:
sebb wrote:
> The MATH code base currently generates hundreds of boxing warnings.
> Many, if not
On 18 July 2013 19:54, Gilles wrote:
> Hi.
>
>
> On Thu, 18 Jul 2013 19:02:34 +0100, sebb wrote:
>>
>> On 18 July 2013 17:56, Mark Thomas wrote:
>>>
>>> sebb wrote:
>>>
The MATH code base currently generates hundreds of boxing warnings.
Many, if not most, are perfectly OK.
For exa
Hi.
On Thu, 18 Jul 2013 19:02:34 +0100, sebb wrote:
On 18 July 2013 17:56, Mark Thomas wrote:
sebb wrote:
The MATH code base currently generates hundreds of boxing warnings.
Many, if not most, are perfectly OK.
For example, conversion of int and long to Number when throwing
various Exceptio
On 18 July 2013 17:56, Mark Thomas wrote:
> sebb wrote:
>
>>The MATH code base currently generates hundreds of boxing warnings.
>>Many, if not most, are perfectly OK.
>>For example, conversion of int and long to Number when throwing
>>various Exceptions.
>>
>>However, buried amongst the valid use
sebb wrote:
>The MATH code base currently generates hundreds of boxing warnings.
>Many, if not most, are perfectly OK.
>For example, conversion of int and long to Number when throwing
>various Exceptions.
>
>However, buried amongst the valid uses there may well be some code
>that is buggy - e.g.
The MATH code base currently generates hundreds of boxing warnings.
Many, if not most, are perfectly OK.
For example, conversion of int and long to Number when throwing
various Exceptions.
However, buried amongst the valid uses there may well be some code
that is buggy - e.g. it uses Long when it
