RFR: JEP 359-Records: reflection code

Vicente Romero vicente.romero at oracle.com
Tue Oct 22 02:40:34 UTC 2019



On 10/21/19 6:32 PM, Maurizio Cimadamore wrote:
>
> On 21/10/2019 23:02, Remi Forax wrote:
>> - the same call works for equals/hashCode and toString, so depending 
>> on the methods some arguments are not used or not
>
> I too found this a bit odd when looking at the javac code - it took me 
> sometime to figure out what was going on.
>
> The question I have here is - is the decision of having a single point 
> a deliberate decision that we think it's going to pay off in the long 
> run? 

it was a deliberate decision, the first implementation actually had 
different bootstrap methods but then we got a table with three bootstrap 
methods per every humble record, so having only one bootstrap method is 
a space gain.
> Or was it more a way to quickly bootstrap the javac implementation? If 
> the latter, we should probably revert to one bootstrap per Object method.
>
> Maurizio
>
Vicente


More information about the amber-dev mailing list