[foreign] RFR duplicates in named layouts have to be reported as error
    Maurizio Cimadamore 
    maurizio.cimadamore at oracle.com
       
    Fri May 25 14:04:36 UTC 2018
    
    
  
As discussed privately, I'm thorn about this:
On the one had it makes the world safer and tidier.
On the other hand, all clients dealing with layouts (including clients 
external to the binder) have to manage Unresolved with hazmat suit - 
which is a marked difference with where we were before.
I wonder if a better compromise can be achieved by associating a context 
to an unresolved layout at parse time?
Maurizio
On 25/05/18 13:48, Sundararajan Athijegannathan wrote:
> If same name is used for two different (group) layouts, LayoutResolver 
> should detect and report error. But different header file interfaces 
> can use the same name.
>
> This is implemented by making LayoutResolver as a ClassValue rather 
> than global.
>
> Webrev: 
> http://cr.openjdk.java.net/~sundar/redefinition_in_named_layouts/webrev.00/
>
> Thanks,
> -Sundar
>
    
    
More information about the panama-dev
mailing list