On Oct 14, 2015, at 3:38 AM, Remi Forax wrote:
>
> Given that j.l.r.Method is mutable, the best way to have performance is too
> encapsulate it in a non mutable class, if possible.
OK, I'll bite. Here's a way to make Method its own non-mutable encapsulation,
a la List::set or (future feature)
Hi,
Just as idea: Why not implement Cloneable for that purpose? Adding new methods
does not look like a good idea.
-
Uwe Schindler
uschind...@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
> -Original Message-
> From: core-libs-dev [
Thanks Paul and Chris,
very interesting indeed.
regards,
Rémi
- Mail original -
> De: "Chris Hegarty"
> À: "Remi Forax"
> Cc: "Paul Sandoz" , "core-libs-dev"
>
> Envoyé: Mercredi 14 Octobre 2015 16:29:15
> Objet: Re: java.lang
On 14 Oct 2015, at 15:15, Remi Forax wrote:
> - Mail original -
>> De: "Paul Sandoz"
>> Cc: "core-libs-dev"
>> Envoyé: Mercredi 14 Octobre 2015 13:46:38
>> Objet: Re: java.lang.reflect.Method.copyOf
>>
>>
>>&
> On 14 Oct 2015, at 16:15, Remi Forax wrote:
>
> - Mail original -
>> De: "Paul Sandoz"
>> Cc: "core-libs-dev"
>> Envoyé: Mercredi 14 Octobre 2015 13:46:38
>> Objet: Re: java.lang.reflect.Method.copyOf
>>
>>
>
- Mail original -
> De: "Paul Sandoz"
> Cc: "core-libs-dev"
> Envoyé: Mercredi 14 Octobre 2015 13:46:38
> Objet: Re: java.lang.reflect.Method.copyOf
>
>
> > On 14 Oct 2015, at 12:38, Remi Forax wrote:
> >
> > Given that j.l.r.Me
> On 14 Oct 2015, at 12:38, Remi Forax wrote:
>
> Given that j.l.r.Method is mutable, the best way to have performance is too
> encapsulate it in a non mutable class, if possible.
>
> As far as i know j.l.r.Method was introduced in Java 1.1 as non mutable and
> become mutable with Java 1.2, (
Given that j.l.r.Method is mutable, the best way to have performance is too
encapsulate it in a non mutable class, if possible.
As far as i know j.l.r.Method was introduced in Java 1.1 as non mutable and
become mutable with Java 1.2, (yes, someone seriously fucked up !)
so methods like copyOf we
