I will still be on the road :) following the JEP draft, I wonder if all functional interfaces (at least the ones tagged with @FunctionalInterface) should also be considered as inline candidates, so synchronizing on them should report a warning too.
the other question is how to declare your own ref class, i.e. how java.lang.int declares that Java.lang.Integer is its ref class ? Does extending a sealed abstract class enough ? regards, remi On August 26, 2020 12:03:17 AM UTC, Dan Smith <daniel.sm...@oracle.com> wrote: >The next EG Zoom meeting is tomorrow, 4pm UTC (9am PDT, 12pm EDT). > >Recent threads to discuss: > >- "IdentityObject & abstract superclasses": I talked about using >IdentityObject as the property that determines whether a class can be >extended by an inline class. JVMs need to automatically apply >IdentityObject to certain abstract classes. > >- "JEP draft: Identity Warnings for Inline Class Candidates": I updated >the JEP to propose a new '@ValueBased' standard annotation. >JEP: https://bugs.openjdk.java.net/browse/JDK-8249100 -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
